From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Testsuite failures in gdb.gdb/selftest.exp
Date: Wed, 31 Jan 2007 19:15:00 -0000 [thread overview]
Message-ID: <20070131191533.GA6608@nevyn.them.org> (raw)
In-Reply-To: <jed54vc8p3.fsf@sykes.suse.de>
On Wed, Jan 31, 2007 at 08:11:52PM +0100, Andreas Schwab wrote:
> Thus the line number information generated by gcc looks correct (address
> 110 is the first insn after the prologue).
It could still be a GCC bug - if the zero is reused for more things
than just that one store, as I hope it will be, then that's a perverse
line number to choose. But that's good enough; thank you for checking.
Patch is OK.
Eli, to answer your question: this is gdb.gdb/selftest.exp, which
debugs the just-compiled GDB binary (which was probably compiled
with optimization). It's one of the few tests of optimized code
that we have in the testsuite.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-31 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 17:12 Andreas Schwab
2007-01-31 17:19 ` Daniel Jacobowitz
2007-01-31 17:55 ` Andreas Schwab
2007-01-31 18:19 ` Daniel Jacobowitz
2007-01-31 19:12 ` Andreas Schwab
2007-01-31 19:15 ` Daniel Jacobowitz [this message]
2007-01-31 19:37 ` Andreas Schwab
2007-01-31 19:00 ` Eli Zaretskii
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=20070131191533.GA6608@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.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