From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29731 invoked by alias); 10 Jan 2006 23:25:41 -0000 Received: (qmail 29718 invoked by alias); 10 Jan 2006 23:25:39 -0000 Date: Tue, 10 Jan 2006 23:25:00 -0000 Message-ID: <20060110232539.29717.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/23451] [3.4/4.0/4.1/4.2 regression] Redundant reloading from stack frame In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "herbert at gondor dot apana dot org dot au" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-01/txt/msg01018.txt.bz2 List-Id: ------- Comment #14 from herbert at gondor dot apana dot org dot au 2006-01-10 23:25 ------- Subject: Re: [3.4/4.0/4.1/4.2 regression] Redundant reloading from stack frame On Tue, Jan 10, 2006 at 10:58:03PM -0000, steven at gcc dot gnu dot org wrote: > > > ------- Comment #8 from steven at gcc dot gnu dot org 2006-01-10 22:58 ------- > Unfortunately you're not showing your full command line, so I can only guess > what platform your host is and for what target you are compiling. I will > attach diffs between GCC 3.2 and GCC 3.3-hammer for i[456]86. To me the > changes look insignificant, but maybe you can point out what you're unhappy > with. Good point. I was using gcc-3.2 -S -O2 which for my build defaults to --march=i386. Indeed, using --march=i486 produces the same output as gcc-3.3/gcc-3.4. In fact, using --march=i386 on gcc-3.3/gcc-3.4 also removes the duplicate reloading. So it seems that it's really a difference between --march=i386 versus --march=i486. Cheers, -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23451