From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22544 invoked by alias); 2 Feb 2005 02:08:06 -0000 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 Received: (qmail 22177 invoked by uid 48); 2 Feb 2005 02:07:58 -0000 Date: Wed, 02 Feb 2005 02:08:00 -0000 Message-ID: <20050202020758.22174.qmail@sourceware.org> From: "yuri at tsoft dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050202015319.19748.yuri@tsoft.com> References: <20050202015319.19748.yuri@tsoft.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/19748] aggressive no-inline options still cause inlining X-Bugzilla-Reason: CC X-SW-Source: 2005-02/txt/msg00152.txt.bz2 List-Id: ------- Additional Comments From yuri at tsoft dot com 2005-02-02 02:07 ------- (In reply to comment #2) > Also note sometimes when a function is pure/const it can be removed which is why it might act as > inlining. > > Do you have a simple example? > ... > Also note sometimes when a function is pure/const it can be removed which is why it might act as > inlining. This const/pure is definitely not my case. I will try to write some example of non-inline. My project is huge, certainly callgrind showed that there is stuff inlined, I will try to reproduce on something smaller. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19748