public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallón" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: Some functions are not inlined by gcc 3.2, resulting code is ugly
Date: Wed, 13 Nov 2002 01:10:59 +0100	[thread overview]
Message-ID: <20021113001059.GA31147@werewolf.able.es> (raw)
In-Reply-To: <200211031322.gA3DMTp28125@Port.imtp.ilyichevsk.odessa.ua>; from vda@port.imtp.ilyichevsk.odessa.ua on Sun, Nov 03, 2002 at 19:14:26 +0100


(sorry to answer to not-final-version mail, but didn't keep the last one.
This also applies, anyway...)

On 2002.11.03 Denis Vlasenko wrote:
> On 3 November 2002 14:17, Denis Vlasenko wrote:
> > It seems gcc started to de-inline large functions.
[...]

> diff -urN linux-2.5.45.orig/include/linux/compiler.h linux-2.5.45fix/include/linux/compiler.h
> --- linux-2.5.45.orig/include/linux/compiler.h	Wed Oct 30 22:43:05 2002
> +++ linux-2.5.45fix/include/linux/compiler.h	Sun Nov  3 15:19:20 2002
> @@ -20,3 +20,11 @@
>      __asm__ ("" : "=g"(__ptr) : "0"(ptr));		\
>      (typeof(ptr)) (__ptr + (off)); })
>  #endif /* __LINUX_COMPILER_H */
> +
> +/* GCC 3 (and probably earlier, I'm not sure) can be told to always inline
> +   a function. */
> +#if __GNUC__ < 3
> +#define force_inline inline
> +#else
> +#define force_inline inline __attribute__ ((always_inline))
> +#endif

This should go before the #endif /* __LINUX_COMPILER_H */, isn't it ?

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-rc1-jam2 (gcc 3.2 (Mandrake Linux 9.1 3.2-3mdk))

  parent reply	other threads:[~2002-11-13  0:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-03 16:17 Some functions are not inlined by gcc 3.2, resulting code is ugly Denis Vlasenko
2002-11-03 16:17 ` Jussi Laako
2002-11-04  0:17   ` Denis Vlasenko
2002-11-03 21:28     ` Jussi Laako
2002-11-04 16:00       ` Denis Vlasenko
2002-11-03 18:14 ` Denis Vlasenko
2002-11-03 15:23   ` Martin J. Bligh
2002-11-04  0:23     ` Denis Vlasenko
2002-11-03 15:37   ` Jakub Jelinek
2002-11-03 16:21     ` Alan Cox
2002-11-04  0:20       ` Denis Vlasenko
2002-11-03 20:28         ` Alan Cox
2002-11-04 16:08           ` Denis Vlasenko
2002-11-13  1:28         ` J.A. Magallón
2002-11-13 11:54           ` Denis Vlasenko
2002-11-13 12:48             ` Denis Vlasenko
2002-11-04  1:21       ` Robert Love
2002-11-04 13:41         ` Alan Cox
2002-11-04 22:44           ` Werner Almesberger
2002-11-04 16:04         ` Denis Vlasenko
2002-11-04 11:39           ` Jakub Jelinek
2002-11-13  0:10   ` J.A. Magallón [this message]
2002-11-13 12:04     ` Denis Vlasenko

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=20021113001059.GA31147@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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