From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11970 invoked by alias); 9 Jan 2011 17:10:50 -0000 Received: (qmail 11954 invoked by uid 22791); 9 Jan 2011 17:10:49 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from ksp.mff.cuni.cz (HELO atrey.karlin.mff.cuni.cz) (195.113.26.206) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 09 Jan 2011 17:10:41 +0000 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 4018) id A340FF0E09; Sun, 9 Jan 2011 18:10:39 +0100 (CET) Date: Sun, 09 Jan 2011 17:19:00 -0000 From: Jan Hubicka To: "hjl.tools at gmail dot com" Cc: gcc-bugs@gcc.gnu.org Subject: Re: [Bug lto/47222] [4.6 Regression] Revision 168593 failed many tests Message-ID: <20110109171039.GC18136@atrey.karlin.mff.cuni.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-IsSubscribed: yes Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-01/txt/msg00824.txt.bz2 > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47222 > > I will take a look. But it still leaves: > > FAIL: gcc.dg/guality/pr36728-1.c -O2 -flto line 12 arg1 == 1 > FAIL: gcc.dg/guality/pr36728-1.c -O2 -flto line 14 arg1 == 1 > FAIL: gcc.dg/guality/pr36728-1.c -O2 -flto -flto-partition=none line 12 arg1 > == 1 > FAIL: gcc.dg/guality/pr36728-1.c -O2 -flto -flto-partition=none line 14 arg1 > == 1 This is probably another case of unwanted optimization. It does not seem to reproduce for me in 64bit mode, I will check 32bit. > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-3.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-apply-4.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-return-1.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-return-1.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-return-1.c -O2 -flto execution test > FAIL: gcc.dg/torture/stackalign/builtin-return-1.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-return-1.c -O2 -flto > -flto-partition=none execution test > FAIL: gcc.dg/torture/stackalign/builtin-return-1.c -O2 -flto > -flto-partition=none execution test What kind of failures are you getting here?