From: Adrian Bunk <bunk@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Alexander van Heukelum <heukelum@mailshack.com>,
jdike@addtoit.com
Subject: Re: [2.6 patch] fs/block_dev.c:I_BDEV() mustn't be inline
Date: Tue, 29 Apr 2008 12:03:27 +0300 [thread overview]
Message-ID: <20080429090327.GA19269@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080429081705.GA3552@uranus.ravnborg.org>
On Tue, Apr 29, 2008 at 10:17:05AM +0200, Sam Ravnborg wrote:
> 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
Previosly we said:
"inline" means "must inline"
With CONFIG_OPTIMIZE_INLINING=y we say:
"inline" means "try a bit harder to inline"
> 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.
gcc anyway has to emit one global copy of this function.
And with the common CONFIG_CC_OPTIMIZE_FOR_SIZE=y we tell gcc to focus
on getting the smallest possible code.
> So I cannot see how the CONFIG_OPTIMIZE_INLINING have any
> effect here.
> It all smells like a gcc bug to me.
The compile error is a gcc bug.
> Sam
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-29 9:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 21:57 [git pull] generic bitops Ingo Molnar
2008-04-24 22:14 ` Linus Torvalds
2008-04-24 22:41 ` Harvey Harrison
2008-04-25 11:12 ` [PATCH] x86, bitops: select the generic bitmap search functions Alexander van Heukelum
2008-04-26 15:15 ` [git pull] generic bitops, take 2 Ingo Molnar
2008-04-26 17:03 ` Linus Torvalds
2008-04-26 17:22 ` Ingo Molnar
2008-04-26 17:28 ` Ingo Molnar
2008-04-26 17:50 ` [git pull] generic bitops, take 3 Ingo Molnar
2008-04-26 17:32 ` [git pull] generic bitops, take 2 Sam Ravnborg
2008-04-26 17:51 ` Miklos Vajna
2008-04-28 15:38 ` [2.6 patch] mm/filemap.c:generic_write_checks() mustn't be inline Adrian Bunk
2008-04-28 15:38 ` [2.6 patch] fs/buffer.c:init_buffer() " Adrian Bunk
2008-04-28 16:01 ` Linus Torvalds
2008-04-28 16:48 ` Adrian Bunk
2008-04-28 16:58 ` Linus Torvalds
2008-04-28 15:38 ` [2.6 patch] fs/block_dev.c:I_BDEV() " Adrian Bunk
2008-04-29 0:41 ` Linus Torvalds
2008-04-29 1:12 ` Al Viro
2008-04-29 1:21 ` Linus Torvalds
2008-04-29 2:32 ` Jeff Dike
2008-04-29 4:57 ` Sam Ravnborg
2008-04-29 8:06 ` Adrian Bunk
2008-04-29 8:17 ` Sam Ravnborg
2008-04-29 9:03 ` Adrian Bunk [this message]
2008-04-28 15:38 ` [2.6 patch] block/blk-barrier.c:blk_ordered_cur_seq() " Adrian Bunk
2008-04-29 7:46 ` Jens Axboe
2008-04-28 15:38 ` [2.6 patch] net/ipv4/ip_output.c:ip_send_check() " Adrian Bunk
2008-04-28 15:38 ` [2.6 patch] reiserfs: some functions " Adrian Bunk
2008-04-29 22:43 ` Edward Shishkin
2008-04-28 15:38 ` [2.6 patch] fs/udf/partition.c:udf_get_pblock() " Adrian Bunk
2008-04-28 16:47 ` Jan Kara
2008-04-28 17:26 ` [git pull] generic bitops, take 2 Jeff Dike
2008-04-26 17:34 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080429090327.GA19269@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=heukelum@mailshack.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®