From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17218 invoked by alias); 10 May 2007 10:04:49 -0000 Received: (qmail 17163 invoked by uid 48); 10 May 2007 10:04:34 -0000 Date: Thu, 10 May 2007 10:04:00 -0000 Message-ID: <20070510100434.17162.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rguenth at gcc dot gnu dot org" 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: 2007-05/txt/msg00770.txt.bz2 ------- Comment #5 from rguenth at gcc dot gnu dot org 2007-05-10 11:04 ------- Confirmed. Either we should not accept always_inline on a function not declared inline (or warn in that case), or a function marked always_inline should be considered for inlining always. Second, the t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function body not available is fixed in 4.1.2. Which leaves us with t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function not inlinable with the function not marked inline (but only for -O0, not -O). I guess we want to make that behavior at least consistent. Note with -O0 -finline we get t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function body not available again ;) -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu dot | |org, hubicka at gcc dot gnu | |dot org Status|WAITING |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-05-10 11:04:34 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886