From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] impressive
Date: Tue, 25 Apr 2006 21:57:08 -0700 [thread overview]
Message-ID: <3e1162e60604252157m50da62dardb98759d7c4152da@mail.gmail.com> (raw)
In-Reply-To: <cc39734bed5352393b40f65a344378c2@quanstro.net>
The main reason that intel and other C compilers implement gcc
extensions is because there is a lot of software that relies on them,
like the linux kernel for instance.
On 4/25/06, erik quanstrom <quanstro@quanstro.net> wrote:
> gcc 4 can be c99 compliant.
>
> gcc '--std=c99' $*
>
> but that doesn't mean that they removed the extensions.
>
> linux is dependent on inline assembly, for example. (i'm not sure why they
> think it necessiary.) so a number of their extensions won't go away. in fact,
> other compilers, like tcc, feel compelled to replicate gnu extensions.
>
> - erik
>
> On Tue Apr 25 15:02:51 CDT 2006, cross@math.psu.edu wrote:
> > On Tue, Apr 25, 2006 at 01:02:30PM +1000, Andy Newman wrote:
> > > I like this quote from the glibc FAQ...
> > >
> > > 1.2. What compiler do I need to build GNU libc?
> > >
> > > ... A lot of extensions of GNU CC are used to increase portability ...
> >
> > I remember a year or two picking up a Linux rag at the train station on the
> > way back from somewhere. They were talking about gcc 4 or something in it
> > and saying how they were hoping to do away with a lot of GNU extensions by
> > stricter adherence to the language standards in the compiler itself; I guess
> > that work got buried. Then again, this was a cursory read on the Subway,
> > and I'm slightly dyslexic, so maybe read it the opposite way it was meant.
> >
> > - Dan C.
> >
>
next prev parent reply other threads:[~2006-04-26 4:57 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 0:26 erik quanstrom
2006-04-26 0:48 ` geoff
2006-04-26 0:54 ` Roman Shaposhnick
2006-04-26 0:53 ` Roman Shaposhnick
2006-04-26 2:15 ` Taj Khattra
2006-04-26 4:59 ` David Leimbach
2006-04-26 12:37 ` Anthony Sorace
2006-04-26 15:28 ` Rian Hunter
2006-04-26 16:39 ` Micah Stetson
2006-04-26 18:02 ` Bruce Ellis
2006-04-26 20:14 ` Micah Stetson
2006-05-08 14:50 ` Harri Haataja
2006-05-08 15:04 ` LiteStar numnums
2006-05-08 15:12 ` Charles Forsyth
2006-05-08 20:08 ` Micah Stetson
2006-05-08 20:52 ` LiteStar numnums
2006-05-08 21:10 ` Jack Johnson
2006-05-08 21:17 ` andrey mirtchovski
2006-05-08 21:18 ` Paul Lalonde
2006-05-08 22:25 ` Francisco J Ballesteros
2006-05-09 21:56 ` Dave Eckhardt
2006-05-10 0:13 ` geoff
2006-05-10 8:39 ` Lluís Batlle
2006-05-08 23:31 ` geoff
2006-05-09 1:18 ` Paul Lalonde
2006-05-09 1:39 ` quanstro
2006-05-09 2:12 ` Paul Lalonde
2006-05-09 2:20 ` quanstro
2006-05-09 3:00 ` Paul Lalonde
2006-05-09 9:32 ` Bruce Ellis
2006-04-26 22:57 ` Roman Shaposhnick
2006-04-26 4:57 ` David Leimbach [this message]
2006-04-26 4:53 ` Ronald G Minnich
2006-04-26 5:11 ` Roman Shaposhnick
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 0:45 erik quanstrom
2006-05-10 2:09 ` Lyndon Nerenberg
2006-05-10 3:35 ` David Arnold
2006-05-10 4:03 ` Lyndon Nerenberg
2006-05-08 22:02 erik quanstrom
2006-04-27 2:13 erik quanstrom
2006-04-27 1:35 erik quanstrom
2006-04-27 1:23 erik quanstrom
2006-04-27 5:08 ` Micah Stetson
2006-04-27 1:10 erik quanstrom
2006-04-27 2:06 ` Jack Johnson
2006-04-26 3:24 jmk
2006-04-26 2:38 erik quanstrom
2006-04-26 0:55 erik quanstrom
2006-04-26 1:07 ` Roman Shaposhnick
2006-04-25 10:20 erik quanstrom
2006-04-25 2:30 erik quanstrom
2006-04-25 2:48 ` Derek Fawcus
2006-04-24 20:37 Ronald G Minnich
2006-04-24 20:51 ` Charles Forsyth
2006-04-24 21:32 ` Brantley Coile
2006-04-25 11:06 ` Anthony Sorace
2006-04-25 11:08 ` Anthony Sorace
2006-04-25 2:15 ` Derek Fawcus
2006-04-25 2:23 ` Roman Shaposhnick
2006-04-25 2:37 ` Derek Fawcus
2006-04-25 3:51 ` Roman Shaposhnick
2006-04-25 8:17 ` Derek Fawcus
2006-04-25 17:53 ` Roman Shaposhnick
2006-04-26 1:11 ` Derek Fawcus
2006-04-26 1:19 ` Roman Shaposhnick
2006-04-26 2:12 ` Derek Fawcus
2006-04-25 3:02 ` Andy Newman
2006-04-25 3:13 ` Ronald G Minnich
2006-04-25 19:57 ` Dan Cross
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=3e1162e60604252157m50da62dardb98759d7c4152da@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).