From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13459 invoked by alias); 11 Mar 2011 12:27:08 -0000 Received: (qmail 13445 invoked by uid 22791); 11 Mar 2011 12:27:07 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 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, 11 Mar 2011 12:27:02 +0000 From: "eblot.ml at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/44768] arm-linux bootstrap broken on expmed.c:157:3: warning ICE X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: eblot.ml at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: CC 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 Date: Fri, 11 Mar 2011 12:27:00 -0000 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-03/txt/msg01113.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44768 Emmanuel Blot changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eblot.ml at gmail dot com --- Comment #9 from Emmanuel Blot 2011-03-11 12:26:58 UTC --- This issue seems to occur on 4.5.x series. I've just got bitten with a similar issue with 4.5.2: a regular static function wrongly recognized as a no-return function: .type nl_upt_process_download_done.clone.0, %function nl_upt_process_download_done.clone.0: @ Function supports interworking. @ Volatile: function does not return. and context is not restored on return Ubuntu team seem to have encounter the same issue with 4.5.1: https://bugs.launchpad.net/bugs/674146 Is there an official fix ongoing for 4.5.3?