This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Testsuite failures in gdb.gdb/selftest.exp
- From: Daniel Jacobowitz <drow at false dot org>
- To: gdb-patches at sourceware dot org
- Date: Wed, 31 Jan 2007 12:19:37 -0500
- Subject: Re: Testsuite failures in gdb.gdb/selftest.exp
- References: <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