This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [patch gas]: Add 'e' for coff targets as section-specifier
>>> On 28.09.11 at 13:21, Kai Tietz <ktietz70@googlemail.com> wrote:
> 2011/9/28 Jan Beulich <JBeulich@suse.com>:
>>>>> On 27.09.11 at 20:35, Kai Tietz <ktietz70@googlemail.com> wrote:
>>> --- /dev/null
>>> +++ src/gas/testsuite/gas/pe/section-exclude.d
>>> @@ -0,0 +1,20 @@
>>> +#objdump: -h
>>> +#name: section exclude
>>> +
>>> +# Test that 'e' works in .section directives.
>>> +
>>> +.*: .*
>>> +
>>> +Sections:
>>> +Idx Name *Size *VMA *LMA *File off *Algn
>>> + 3 .foo1 00000004 0000000000000000 0000000000000000 000000b4
>>> 2**2
>>> + CONTENTS, EXCLUDE
>>> + 0 \.text 0*0000000 0*0000000 0*0000000 0*0000000 2\*\*[24]
>>> +.*
>>> + 1 \.data 0*0000000 0*0000000 0*0000000 0*0000000 2\*\*[24]
>>> +.*
>>> + 2 \.bss 0*0000000 0*0000000 0*0000000 0*0000000 2\*\*[24]
>>> +.*
>>> + 3 \.foo1 0*0000004 0*0000000 0*0000000 0*0000000 2\*\*[24]
>>> +.*CONTENS, EXCLUDE
>>> +.*
>>
>> This new test causes
>>
>> Running
> /home/jbeulich/cpp/binutils/mainline-cvs/2011-09-28/gas/testsuite/gas/pe/p
> e.exp ...
>> ERROR: tcl error sourcing
> /home/jbeulich/cpp/binutils/mainline-cvs/2011-09-28/gas/testsuite/gas/pe/p
> e.exp.
>> ERROR: couldn't compile regular expression pattern: quantifier operand
> invalid
>> while executing
>> "regexp "^$line_bx$" "$line_a""
>> (procedure "regexp_diff" line 106)
>> invoked from within
>> "regexp_diff "dump.out" "${dumpfile}" $regexp_subst"
>> (procedure "run_dump_test" line 329)
>> invoked from within
>> "run_dump_test "section-exclude""
>> (file
> "/home/jbeulich/cpp/binutils/mainline-cvs/2011-09-28/gas/testsuite/gas/pe/
> pe.exp" line 38)
>> invoked from within
>> "source
> /home/jbeulich/cpp/binutils/mainline-cvs/2011-09-28/gas/testsuite/gas/pe/p
> e.exp"
>> ("uplevel" body line 1)
>> invoked from within
>> "uplevel #0 source
> /home/jbeulich/cpp/binutils/mainline-cvs/2011-09-28/gas/testsuite/gas/pe/p
> e.exp"
>> invoked from within
>> "catch "uplevel #0 source $test_file_name""
>>
>> on an older system of mine.
>>
>> Jan
>
> Not sure what you are seeing here. I can't reproduce this. For what
> target you are building here?
I'm seeing this for cross-builds (on Linux) for all *-pe targets I tried. I
was actually thinking that the (older) version of some package on this
system may be the culprit (where I don't such a dependency should
be introduced with a test case).
Besides that I'm sort of surprised this works at all, because the first of
the sections to match (oddly enough with an index of 3) appears to
duplicate the last one, just missing the regex escapes and the [24]
widening of the permitted alignment. And the second to last line has
an apparent spelling mistake (CONTENS instead of CONTENTS).
Jan