From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org, Terrence.Miller@sun.com
Cc: Jakub Jelinek <jakub@redhat.com>, Adrian Bunk <bunk@stusta.de>,
Michael Matz <matz@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [discuss] [2.6 patch] include/asm-x86_64 "extern inline" -> "static inline"
Date: Tue, 6 Sep 2005 23:49:00 +0200 [thread overview]
Message-ID: <200509062349.01517.ak@suse.de> (raw)
In-Reply-To: <431E023E.3050301@Sun.COM>
On Tuesday 06 September 2005 22:55, Terrence Miller wrote:
> Andi Kleen wrote:
> > I don't think the functionality of having single copies in case
> > an out of line version was needed was ever required by the Linux kernel.
>
> But shouldn't the compiler that compiles Linux be C99 compliant?
At least the kernel and some core functionality (glibc) has been
traditionally written in GNU C, not ISO C. So no, that is not
a design goal.
Of course on the other hand GNU C is getting more and more like
ISO C with the gcc people dropping extensions over time.
Some of the extension use is probably more by mistake, but
others (like typeof, inline assembly, statement expressions) are widely
and intentionally used and would be quite hard to replace.
However people have built the kernel with non gcc compilers,
it just needed extensive modifications to either the compiler
or the kernel.
-Andi
next prev parent reply other threads:[~2005-09-06 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 20:31 [2.6 patch] include/asm-x86_64 "extern inline" -> "static inline" Adrian Bunk
2005-09-05 8:52 ` [discuss] " Michael Matz
2005-09-05 18:00 ` Adrian Bunk
2005-09-05 18:47 ` Jakub Jelinek
2005-09-05 19:00 ` Adrian Bunk
2005-09-06 4:38 ` H. Peter Anvin
2005-09-06 17:54 ` Terrence Miller
2005-09-06 20:23 ` Andi Kleen
2005-09-06 20:32 ` David S. Miller
2005-09-06 20:55 ` Terrence Miller
2005-09-06 21:41 ` Michael Matz
2005-09-07 0:07 ` H. Peter Anvin
2005-09-06 21:49 ` Andi Kleen [this message]
2005-09-05 23:25 ` 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=200509062349.01517.ak@suse.de \
--to=ak@suse.de \
--cc=Terrence.Miller@sun.com \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
/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