From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4: always_inline for gcc3
Date: Tue, 26 Aug 2003 09:15:31 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308260850170.3191@logos.cnet> (raw)
In-Reply-To: <20030826082459.GC2017@werewolf.able.es>
Can you please explain me what are the differences when using "__inline__
__attribute__((always_inline))" and why you chose to use that?
On Tue, 26 Aug 2003, J.A. Magallon wrote:
> Hi.
>
> Resending for 2.4.23-pre ;)
>
> --- 25/include/linux/compiler.h~gcc3-inline-fix 2003-03-06
> 03:02:43.000000000 -0800
> +++ 25-akpm/include/linux/compiler.h 2003-03-06 03:11:42.000000000 -0800
> @@ -1,6 +1,13 @@
> #ifndef __LINUX_COMPILER_H
> #define __LINUX_COMPILER_H
>
> +#if __GNUC__ >= 3
> +#define inline __inline__ __attribute__((always_inline))
> +#define inline__ __inline__ __attribute__((always_inline))
> +#define __inline __inline__ __attribute__((always_inline))
> +#define __inline__ __inline__ __attribute__((always_inline))
> +#endif
> +
> /* Somewhere in the middle of the GCC 2.96 development cycle, we implemented
> a mechanism by which the user can annotate likely branch directions and
> expect the blocks to be reordered appropriately. Define __builtin_expect
>
>
>
next prev parent reply other threads:[~2003-08-26 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 8:24 J.A. Magallon
2003-08-26 12:15 ` Marcelo Tosatti [this message]
2003-08-26 16:24 ` J.A. Magallon
2003-08-26 17:00 ` J.A. Magallon
2003-08-27 14:37 ` Alan Cox
2003-08-27 16:14 ` J.A. Magallon
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=Pine.LNX.4.44.0308260850170.3191@logos.cnet \
--to=marcelo@conectiva.com.br \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.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®