From: dewar@gnat.com
To: jbuck@racerx.synopsys.com, torvalds@transmeta.com
Cc: gcc@gcc.gnu.org
Subject: Re: Trigraph warnings when compiling linux-2.4.0-prerelease1
Date: Tue, 02 Jan 2001 09:26:00 -0000 [thread overview]
Message-ID: <20010102172602.3A34434D86@nile.gnat.com> (raw)
<<Well, at least, it's not a serious one. And if you want to claim that
the kernel is not written in C, but rather in a language dialect called,
say, gcc258, it's not a bug.
>>
The name of the language is GNU C, and it is perfectly reasonable for
GNU tools and related software to be written in this language. The only
tools that really need to stay with in the confines of traditional C
(ANSI C is already too large) are the compiler itself, so that everything
can be bootstrapped.
But there is really no interest in compiling the kernel with some other
compiler other than the gcc GNU C compiler as far as I can see.
next reply other threads:[~2001-01-02 9:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 9:26 dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 13:27 dewar
2001-01-02 15:20 ` Joe Buck
2001-01-02 19:03 ` Fergus Henderson
2001-01-03 11:21 ` Joe Buck
2001-01-02 12:05 dewar
[not found] <200101020654.WAA03344@neosilicon.transmeta.com>
2001-01-01 23:00 ` Linus Torvalds
2001-01-02 0:23 ` Fergus Henderson
2001-01-02 9:18 ` Joe Buck
2001-01-02 10:38 ` Linus Torvalds
2001-01-02 10:58 ` Joe Buck
2001-01-02 11:15 ` Linus Torvalds
2001-01-02 11:50 ` Per Bothner
2001-01-02 11:55 ` Linus Torvalds
2001-01-02 12:40 ` Joe Buck
2001-01-02 13:50 ` Linus Torvalds
2001-01-02 14:50 ` Toon Moene
2001-01-03 23:39 ` Zack Weinberg
2001-01-01 9:56 Rich Baum
2001-01-01 11:50 ` Tim Hollebeek
2001-01-01 15:16 ` Joe Buck
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=20010102172602.3A34434D86@nile.gnat.com \
--to=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@racerx.synopsys.com \
--cc=torvalds@transmeta.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).