From: Andreas Schwab <schwab@suse.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: can someone explain "inline" once and for all?
Date: Fri, 19 Jan 2007 14:37:29 +0100 [thread overview]
Message-ID: <jefya7jfxi.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0701190645400.24224@CPE00045a9c397f-CM001225dbafb6> (Robert P. J. Day's message of "Fri, 19 Jan 2007 06:56:54 -0500 (EST)")
"Robert P. J. Day" <rpjday@mindspring.com> writes:
> first, there appear to be three possible ways of specifying an
> inline routine in the kernel source:
>
> $ grep -r "static inline " .
> $ grep -r "static __inline__ " .
> $ grep -r "static __inline " .
>
> i vaguely recall that this has something to do with a distinction
> between C99 inline and gcc inline
No, it doesn't (there is no C99 compatible inline in gcc before 4.3). It
has to do with the fact that inline is not a keyword in C89, so you need
to use a different spelling when you want to stay compatible with strict
C89.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-01-19 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 11:56 can someone explain "inline" once and for all? Robert P. J. Day
2007-01-19 13:01 ` Pekka Enberg
2007-01-19 13:19 ` Robert P. J. Day
2007-01-19 14:13 ` Adrian Bunk
2007-01-19 14:44 ` Robert P. J. Day
2007-01-19 14:53 ` Robert P. J. Day
2007-01-19 13:37 ` Andreas Schwab [this message]
2007-01-19 13:48 ` Robert P. J. Day
2007-01-19 13:58 ` Andreas Schwab
2007-01-19 14:00 ` Robert P. J. Day
2007-01-19 17:15 ` Alexandre Oliva
2007-01-19 17:36 ` 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=jefya7jfxi.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.