This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Testsuite failures in gdb.gdb/selftest.exp


Daniel Jacobowitz <drow@false.org> writes:

> 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?

On ia64 the address of gdb_stdout/gdb_stderr (together with a few other
variables) is definitely computed very early in the function.  The
quit_flag case could indeed be an instance of the gcc bug.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]