public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Mikael Starvik <mikael.starvik@axis.com>
Cc: dev-etrax <dev-etrax@axis.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] cris: "extern inline" -> "static inline"
Date: Mon, 22 Aug 2005 13:57:24 +0200	[thread overview]
Message-ID: <20050822115724.GJ5726@stusta.de> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66801B764F8@exmail1.se.axis.com>

On Mon, Aug 22, 2005 at 07:08:30AM +0200, Mikael Starvik wrote:

> At the time this is rejected because GCC 3.2 makes other inlining
> descisions when "extern inline" is used instead of "static inline".
> Actually we modified lots of static inline to extern inline in
> 2.4 in November 2002 to reduce code bloat with GCC 3.2. I don't
> know if this still is true with 4.0. 
>...

If you look at include/linux/compiler-gcc3.h, you see that in the 
kernel, we #define "inline" to "inline __attribute__((always_inline))"
for gcc >= 3.1 .

In November 2002, we didn't do this in 2.4 kernels.

Can you test whether my patch makes any difference in the size of a 2.6 
kernel with gcc 3.2?

> /Mikael
>...

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


  reply	other threads:[~2005-08-22 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BFECAF9E178F144FAEF2BF4CE739C66803297EF0@exmail1.se.axis.com>
2005-08-22  5:08 ` [2.6 patch] cris: "extern inline" -> "static inline" Mikael Starvik
2005-08-22 11:57   ` Adrian Bunk [this message]
2005-10-31 16:24 Adrian Bunk
     [not found] <BFECAF9E178F144FAEF2BF4CE739C66803297EF2@exmail1.se.axis.com>
2005-08-23  9:36 ` Mikael Starvik
  -- strict thread matches above, loose matches on Subject: below --
2005-08-21 23:54 Adrian Bunk

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=20050822115724.GJ5726@stusta.de \
    --to=bunk@stusta.de \
    --cc=dev-etrax@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.com \
    /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