From: Rob Landley <landley@webofficenow.com>
To: Andrea Arcangeli <andrea@suse.de>,
Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: user-mode port 0.44-2.4.7
Date: Mon, 23 Jul 2001 09:20:32 -0400 [thread overview]
Message-ID: <01072309203206.00996@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0107231259520.13272-100000@penguin.transmeta.com> <200107232150.f6NLosh13126@vindaloo.ras.ucalgary.ca> <20010724000933.I16919@athlon.random>
In-Reply-To: <20010724000933.I16919@athlon.random>
On Monday 23 July 2001 18:09, Andrea Arcangeli wrote:
> GCC will obviously _never_ introduce a BUG(), I never said that, the
> above example is only meant to show what GCC is _allowed_ to do and what
> we have to do to write correct C code.
"Correct" C code as in portable C code? Standards compliant so it's portable
to other compilers?
The linux kernel is compiled on gcc. It always has been. Specific versions
of the kernel have a specific range of "known working" gcc versions that in
the past have produced a functional result. gcc is -ALLOWED- to compile code
the way Borland, Watcom, or Microsoft C compilers do. Assuming somebody
wants to rewrite gcc from scratch and still call the result gcc...
Standards are fun, but we don't even thread posixly yet...
Rob
next prev parent reply other threads:[~2001-07-23 22:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 5:08 user-mode port 0.44-2.4.7 Jeff Dike
2001-07-23 15:56 ` Andrea Arcangeli
2001-07-23 15:59 ` Andrea Arcangeli
2001-07-23 16:17 ` Andrea Arcangeli
2001-07-23 16:51 ` Andrea Arcangeli
2001-07-23 16:33 ` Linus Torvalds
2001-07-23 16:45 ` Andrea Arcangeli
2001-07-23 17:32 ` Linus Torvalds
2001-07-23 17:50 ` Andrea Arcangeli
2001-07-23 18:11 ` Linus Torvalds
2001-07-23 18:27 ` Andrea Arcangeli
2001-07-23 20:00 ` Linus Torvalds
2001-07-23 20:15 ` Jonathan Lundell
2001-07-23 22:51 ` Linus Torvalds
2001-07-24 3:45 ` Jonathan Lundell
2001-07-24 15:41 ` Davide Libenzi
2001-07-24 15:46 ` Alexander Viro
2001-07-24 16:01 ` Davide Libenzi
2001-07-24 16:08 ` Alexander Viro
2001-07-24 16:52 ` Davide Libenzi
2001-07-24 16:59 ` Linus Torvalds
2001-07-24 17:31 ` Davide Libenzi
2001-07-24 17:38 ` Linus Torvalds
2001-07-24 18:07 ` Anton Altaparmakov
2001-07-23 20:44 ` Chris Friesen
2001-07-23 21:11 ` Andrea Arcangeli
2001-07-23 21:50 ` Richard Gooch
2001-07-23 22:09 ` Andrea Arcangeli
2001-07-23 13:20 ` Rob Landley [this message]
2001-07-23 22:27 ` Andrea Arcangeli
2001-07-23 17:50 ` Rob Landley
2001-07-23 23:47 ` Richard Gooch
2001-07-24 0:04 ` Andrea Arcangeli
2001-07-24 9:02 ` Jan Hubicka
2001-07-24 15:35 ` Linus Torvalds
2001-07-24 16:04 ` Linus Torvalds
2001-07-25 22:49 ` Andrea Arcangeli
2001-07-25 23:16 ` Linus Torvalds
2001-07-25 23:37 ` Chris Friesen
2001-07-26 18:28 ` Jan Hubicka
2001-07-26 18:35 ` Alan Cox
2001-07-23 22:53 ` Linus Torvalds
2001-07-23 23:13 ` Alan Cox
2001-07-23 20:25 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2001-07-25 19:03 James W. Lake
[not found] <no.id>
2001-07-23 20:57 ` Alan Cox
2001-07-23 21:14 ` Chris Friesen
2001-07-25 19:12 ` Alan Cox
2001-07-25 23:49 ` Alan Cox
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=01072309203206.00996@localhost.localdomain \
--to=landley@webofficenow.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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.