From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760533AbYD2IQu (ORCPT ); Tue, 29 Apr 2008 04:16:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755547AbYD2IQe (ORCPT ); Tue, 29 Apr 2008 04:16:34 -0400 Received: from pasmtpa.tele.dk ([80.160.77.114]:57291 "EHLO pasmtpA.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755482AbYD2IQd (ORCPT ); Tue, 29 Apr 2008 04:16:33 -0400 Date: Tue, 29 Apr 2008 10:17:05 +0200 From: Sam Ravnborg To: Adrian Bunk Cc: Linus Torvalds , Ingo Molnar , Linux Kernel Mailing List , Andrew Morton , Thomas Gleixner , "H. Peter Anvin" , Alexander van Heukelum , jdike@addtoit.com Subject: Re: [2.6 patch] fs/block_dev.c:I_BDEV() mustn't be inline Message-ID: <20080429081705.GA3552@uranus.ravnborg.org> References: <20080424215739.GA32378@elte.hu> <20080426151516.GA27894@elte.hu> <20080426172222.GD17345@elte.hu> <20080428153831.GC2813@cs181133002.pp.htv.fi> <20080429080631.GB28059@cs181133002.pp.htv.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080429080631.GB28059@cs181133002.pp.htv.fi> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 29, 2008 at 11:06:31AM +0300, Adrian Bunk wrote: > On Mon, Apr 28, 2008 at 05:41:11PM -0700, Linus Torvalds wrote: > >... > > > -inline struct block_device *I_BDEV(struct inode *inode) > > > +struct block_device *I_BDEV(struct inode *inode) > > > { > > > return &BDEV_I(inode)->bdev; > > > } > > > > There is NO WAY IN HELL this function shouldn't be inlined, > >... > > Then CONFIG_OPTIMIZE_INLINING already broke it in your tree. Can you please help me here. Previously we said: gcc shall inline Now we say: hi gcc - it is a good idea to inline this But even without any inline annotation we would expect gcc to inline it based on normal heuristics simply due to the small size/footprint of the function. So I cannot see how the CONFIG_OPTIMIZE_INLINING have any effect here. It all smells like a gcc bug to me. Sam