From: dje@google.com
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix rereading of DWO DIEs
Date: Thu, 19 Jul 2012 16:17:00 -0000 [thread overview]
Message-ID: <20488.13038.452382.101032@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <m2wr20jhkt.fsf@igel.home>
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]
2012-07-19 Doug Evans <dje@google.com>
* gdb.dwarf2/fission-reread.S: Use .data instead of .bss.
* gdb.dwarf2/pr13961.S: Ditto.
Index: fission-reread.S
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.dwarf2/fission-reread.S,v
retrieving revision 1.4
diff -u -p -r1.4 fission-reread.S
--- fission-reread.S 15 Jul 2012 08:34:55 -0000 1.4
+++ fission-reread.S 19 Jul 2012 16:13:19 -0000
@@ -41,7 +41,7 @@
.file "fission-reread.cc"
.globl baz
- .bss
+ .data /* Previously this used .bss, but it's not portable. */
.align 4
.type baz, @object
.size baz, 4
Index: pr13961.S
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.dwarf2/pr13961.S,v
retrieving revision 1.2
diff -u -p -r1.2 pr13961.S
--- pr13961.S 3 May 2012 06:49:05 -0000 1.2
+++ pr13961.S 19 Jul 2012 16:13:19 -0000
@@ -40,7 +40,7 @@
.file "pr13961.cc"
.globl baz
- .bss
+ .data /* Previously this used .bss, but it's not portable. */
.align 4
.type baz, @object
.size baz, 4
next prev parent reply other threads:[~2012-07-19 16:17 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 [this message]
2012-07-19 16:41 ` Andreas Schwab
2012-07-19 17:24 ` Doug Evans
2012-07-30 16:58 ` Doug Evans
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=20488.13038.452382.101032@ruffy2.mtv.corp.google.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