mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: ncunningham@linuxmail.org, ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch]  kill __always_inline
Date: Thu, 2 Sep 2004 21:46:00 +0200	[thread overview]
Message-ID: <20040902194600.GE15358@fs.tum.de> (raw)
In-Reply-To: <20040831163914.4c7c543c.akpm@osdl.org>

On Tue, Aug 31, 2004 at 04:39:14PM -0700, Andrew Morton wrote:
> Nigel Cunningham <ncunningham@linuxmail.org> wrote:
> >
> > Hi.
> > 
> > On Wed, 2004-09-01 at 08:52, Adrian Bunk wrote:
> > > On Tue, Aug 31, 2004 at 03:36:49PM -0700, Andrew Morton wrote:
> > > > Adrian Bunk <bunk@fs.tum.de> wrote:
> > > > >
> > > > > An issue that we already discussed at 2.6.8-rc2-mm2 times:
> > > > > 
> > > > > 2.6.9-rc1 includes __always_inline which was formerly in  -mm.
> > > > > __always_inline doesn't make any sense:
> > > > > 
> > > > > __always_inline is _exactly_ the same as __inline__, __inline and inline .
> > > > > 
> > > > > 
> > > > > The patch below removes __always_inline again:
> > > > 
> > > > But what happens if we later change `inline' so that it doesn't do
> > > > the `always inline' thing?
> > > > 
> > > > An explicit usage of __always_inline is semantically different than
> > > > boring old `inline'.
> > 
> > Excuse me if I'm being ignorant, but I thought always_inline was
> > introduced because with some recent versions of gcc, inline wasn't doing
> > the job (suspend2, which requires a working inline, was broken by it for
> > example).
> 
> IIRC, the compiler was generating out-of-line versions of functions in
> every compilation unit whcih included the header file.  When we the
> developers just wanted `inline' to mean `inline, dammit'.

`inline, dammit' is
  __attribute__((always_inline))

The original `inline' never guarantees that the function will be 
inlined.

Therefore, `inline' is already #define'd in the Linux kernel to always 
be __attribute__((always_inline)).

> If that broke swsusp in some manner then the relevant swsusp functions
> should be marked always_inline, because they have some special needs.
> 
> > That is to say, doesn't the definition of always_inline vary
> > with the compiler version?
> 
> If the compiler supports attribute((always_inline)) then the kernel build
> system will use that.  If the compiler doesn't support
> attribute((always_inline)) then we just emit `inline' from cpp and hope
> that it works out.

That's exactly how `inline' is already #define'd in the Linux kernel.

And __always_inline is currently simply #define'd to `inline' ...

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


  parent reply	other threads:[~2004-09-02 19:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 22:13 Adrian Bunk
2004-08-31 22:36 ` Andrew Morton
2004-08-31 22:52   ` Adrian Bunk
2004-08-31 23:01     ` Andrew Morton
2004-08-31 23:12     ` Nigel Cunningham
2004-08-31 23:39       ` Andrew Morton
2004-08-31 23:41         ` Nigel Cunningham
2004-09-02 19:46         ` Adrian Bunk [this message]
2004-09-02 23:12           ` Tim Bird
2004-09-02 23:25             ` Andrew Morton
     [not found] <2zpiO-72f-37@gated-at.bofh.it>
     [not found] ` <2zpC1-7fh-13@gated-at.bofh.it>
     [not found]   ` <2zpVj-7yW-3@gated-at.bofh.it>
     [not found]     ` <2zqeK-7JB-3@gated-at.bofh.it>
2004-08-31 23:43       ` Andi Kleen

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=20040902194600.GE15358@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.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

Powered by JetHome