From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21658 invoked by alias); 31 Jan 2007 17:19:45 -0000 Received: (qmail 21644 invoked by uid 22791); 31 Jan 2007 17:19:44 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 31 Jan 2007 17:19:39 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1HCJ7R-00007d-PJ for gdb-patches@sourceware.org; Wed, 31 Jan 2007 12:19:37 -0500 Date: Wed, 31 Jan 2007 17:19:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sourceware.org Subject: Re: Testsuite failures in gdb.gdb/selftest.exp Message-ID: <20070131171937.GA337@nevyn.them.org> Mail-Followup-To: gdb-patches@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00615.txt.bz2 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