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 17:19:00 -0000 [thread overview]
Message-ID: <20070131171937.GA337@nevyn.them.org> (raw)
In-Reply-To: <jed54v86ii.fsf@sykes.suse.de>
On Wed, Jan 31, 2007 at 06:12:37PM +0100, Andreas Schwab wrote:
> With heavy optimizations there can be even more code reordering, causing
> spurious failures in do_steps_and_nexts.
>
> The quit_flag case was seen on ppc, the gdb_std{out,err} cases on ia64.
You may have checked this already but... are these sensible lines to
have reached, given what's executing? Or are these additional
symptoms of gcc/26475 or a similar problem?
I can't see how a non-interprocedural optimizer would do anything
useful with any of those statements across an extern call to xmalloc.
But on ia64 it might be e.g. computing the address of stdout before
the call, given how many registers there are.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-31 17:19 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 [this message]
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
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=20070131171937.GA337@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