From: Doug Evans <dje@google.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix rereading of DWO DIEs
Date: Mon, 30 Jul 2012 16:58:00 -0000 [thread overview]
Message-ID: <CADPb22TnMAfoJRxbGzXcDZ98Ci3=6JPMjeuxvwR==VgLVu+35g@mail.gmail.com> (raw)
In-Reply-To: <CADPb22QLt-eJh==BaaVKOx2NYsimzrpnngXUvP2=BUVEmyOQzA@mail.gmail.com>
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.
prev parent reply other threads:[~2012-07-30 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 2:18 Doug Evans
2012-07-02 8:34 ` [patch 1/2] testcase: Make it -m32 compatible [Re: [commit] Fix rereading of DWO DIEs] Jan Kratochvil
2012-07-02 8:38 ` Jan Kratochvil
2012-07-02 20:10 ` [commit] " Jan Kratochvil
2012-07-02 8:35 ` [patch 2/2] testcase: Make it cross-arch " Jan Kratochvil
2012-07-02 20:11 ` [commit] " Jan Kratochvil
2012-07-19 8:12 ` [commit] Fix rereading of DWO DIEs Andreas Schwab
2012-07-19 16:17 ` dje
2012-07-19 16:41 ` Andreas Schwab
2012-07-19 17:24 ` Doug Evans
2012-07-30 16:58 ` Doug Evans [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADPb22TnMAfoJRxbGzXcDZ98Ci3=6JPMjeuxvwR==VgLVu+35g@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox