From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24909 invoked by alias); 15 Jan 2008 15:48:04 -0000 Received: (qmail 24690 invoked by uid 48); 15 Jan 2008 15:47:17 -0000 Date: Tue, 15 Jan 2008 16:08:00 -0000 Message-ID: <20080115154717.24689.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/18071] [4.0/4.1/4.2/4.3 Regression] -Winline does not respect -fno-default-inline In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hubicka 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: 2008-01/txt/msg01508.txt.bz2 ------- Comment #32 from hubicka at gcc dot gnu dot org 2008-01-15 15:47 ------- I am bit confused by logic of code here. Middle end now ingore DECL_INLINE consistently, it is still arround since it affect some instantiation decisions in C++ FE. Does fno-default-inline work? I think only way to prevent inlining is to make C++ frontend to drop implicit noinline attribute or split the two meanings of DECL_DECLARED_INLINE (ie meaning to drive inliner and to drive linkage). As I understand it now, DECL_DECLARED_INLINE must be always set for functions that are implicitly inline, even with -fno-default-inline, because it affects linkage, right? Honza -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18071