This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

New failures with .debug_ranges test


Hi Andrew,

  I am seeing some new failures in the binutils testsuite for several
  targets:

Checking Binutils in: msp430-elf ... LD: 1 BIN: 1 done
 BIN REGRESSION: objdump -W for debug_ranges 

Checking Binutils in: nds32le-elf ... GAS: 9 LD: 15 BIN: 5 done
 BIN REGRESSION: objdump -W for debug_ranges 

Checking Binutils in: sh64-superh-linux-gnu ... GAS: 6 LD: 14 BIN: 7 done
 BIN REGRESSION: objdump -W for debug_ranges 


  The failures are all regexp matching problems.  eg for the msp430:

regexp_diff match failure
regexp "^    00000000 00000004 00000008 $"
line   "    00000000 00000004 00000010 "
regexp_diff match failure
regexp "^    00000000 00000008 0000000c $"
line   "    00000000 00000008 0000001c "


  For nds32:

regexp_diff match failure
regexp "^  \[0x.*\]  Extended opcode 2: set Address to 0x4$"
line   "  [0x0000002d]  Extended opcode 2: set Address to 0x0"
regexp_diff match failure
regexp "^  \[0x.*\]  Extended opcode 2: set Address to 0x8$"
line   "  [0x00000038]  Extended opcode 2: set Address to 0x0"

  For sh64:

regexp_diff match failure
regexp "^  \[0x.*\]  Extended opcode 2: set Address to 0x4$"
line   "  [0x0000002d]  Extended opcode 2: set Address to 0x5"
regexp_diff match failure
regexp "^  \[0x.*\]  Extended opcode 2: set Address to 0x8$"
line   "  [0x00000038]  Extended opcode 2: set Address to 0x9"


Please could you have a look at these and determine if these targets are
broken, or if the test is making a bad assumption about the output.

Cheers
  Nick


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]