Re: [commit] Fix rereading of DWO DIEs

Doug Evans
2012-07-30T16:58:50Z

On Thu, Jul 19, 2012 at 10:24 AM, Doug Evans <dje@google.com> wrote:
> On Thu, Jul 19, 2012 at 9:40 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> dje@google.com writes:
>>
>>> Andreas Schwab writes:
>>> > Executing on host: gcc -c -o /home/abuild/rpmbuild/BUILD/gdb-7.4.91/gdb/testsuite/gdb.dwarf2/fission-reread0.o ./gdb.dwarf2/fission-reread.S (timeout = 300)
>>> > spawn gcc -c -o /home/abuild/rpmbuild/BUILD/gdb-7.4.91/gdb/testsuite/gdb.dwarf2/fission-reread0.o ./gdb.dwarf2/fission-reread.S
>>> > fission-reread.cc: Assembler messages:
>>> > fission-reread.cc:44: Error: unknown pseudo-op: `.bss'
>>> > compiler exited with status 1
>>> > output is:
>>> > fission-reread.cc: Assembler messages:
>>> > fission-reread.cc:44: Error: unknown pseudo-op: `.bss'
>>> >
>>> > gdb compile failed, fission-reread.cc: Assembler messages:
>>> > fission-reread.cc:44: Error: unknown pseudo-op: `.bss'
>>> > UNTESTED: gdb.dwarf2/fission-reread.exp: fission-reread.exp
>>>
>>> Hi.
>>>
>>> Can you test this?
>>> [.data is used elsewhere so this should be portable enough]
>>
>> Or .section .bss.
>
> There is no occurrence of the word "bss" in any gdb.dwarf2/*.S files
> outside the two files in question, so for consistency's sake I went
> with .data.

Committed to cvs head and 7.5 branch.