From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9692 invoked by alias); 4 Nov 2011 17:08:51 -0000 Received: (qmail 9677 invoked by uid 22791); 4 Nov 2011 17:08:49 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_GJ X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Nov 2011 17:08:36 +0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50925] [4.7 Regression][avr] ICE at spill_failure, at reload1.c:2118 Date: Fri, 04 Nov 2011 17:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Target Status Known to work Keywords Last reconfirmed CC Ever Confirmed Summary Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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-11/txt/msg00411.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50925 Georg-Johann Lay changed: What |Removed |Added ---------------------------------------------------------------------------- Target|avr-rtems4.11 |avr-* Status|UNCONFIRMED |NEW Known to work| |4.6.2 Keywords| |ice-on-valid-code Last reconfirmed| |2011-11-04 CC| |gjl at gcc dot gnu.org Ever Confirmed|0 |1 Summary|avr ICE at spill_failure, |[4.7 Regression][avr] ICE |at reload1.c:2118 |at spill_failure, at | |reload1.c:2118 --- Comment #3 from Georg-Johann Lay 2011-11-04 17:08:30 UTC --- I can confirm this on current trunk r180962 with -Os/-O2/-O3. The bug disappears with -fno-caller-saves. I already observed trouble with -fcaller-saves together with -mstrict-X so that perhaps it is a good idea to disable that option for AVR? A size comparison if avr-libc generated with -f[no-]caller-saves looks as follows: Columns: 3nd = #bytes with -fcaller-saves 3rd = #bytes with -fno-caller-saves 4th = relative size gain 5th = absolute size gain vfscanf_flt.o : 21197 21347 0.7% 150 realloc.o : 4110 4164 1.3% 54 vfprintf_std.o : 8858 8840 -0.2% -18 vfprintf_flt.o : 16604 16508 -0.6% -96 calloc.o : 636 540 -15.1% -96 strdup.o : 654 516 -21.1% -138 vfscanf_min.o : 9613 9433 -1.9% -180 vfscanf_std.o : 12918 12736 -1.4% -182 :::::: Total ::::::: : 322839 322333 -0.2% -506 Other object do not change in size. Denis, what do you think: Should we kick off caller-saves alltogether? Appears that option increases register pressure/spill requests up to a level not appropriate for AVR.