From: Linus Torvalds <torvalds@transmeta.com>
To: Joe Buck <jbuck@racerx.synopsys.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Trigraph warnings when compiling linux-2.4.0-prerelease1
Date: Tue, 02 Jan 2001 10:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10101021032090.25012-100000@penguin.transmeta.com> (raw)
In-Reply-To: <200101021716.JAA08765@racerx.synopsys.com>
On Tue, 2 Jan 2001, Joe Buck wrote:
> > >> line 929: printk("imm: parity error (???)\n");
> > >> line 938: printk("imm: bad interrupt (???)\n");
> > >
> > >This is a kernel bug. That is, a strict ISO C compiler
> > >must print
> > >
> > >imm: bad interrupt (?]
> >
> > This is NOT a kernel bug.
>
> 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.
Ehh..
The compiler is called "gcc", and is invoced as such.
And you apparently entirely dismissed the fact that the Linux behaviour is
based on _documented_ behaviour. And you still want to call it a "bug".
> It's more important to alert users that their code may malfunction if
> they compile it with a different compiler than to produce a warning-free
> compile of the Linux kernel. It's a tradeoff. The kernel is only one
> program.
The kernel may be one program, but point me to a _single_ program that
uses trigraphs. Show me _one_ serious program that wants to use them.
The fact is, nobody uses trigraphs. NOBODY. They were a bad idea.
But hey, as good as you are at ignoring documentation, I'm sure you'll
have no trouble at all ignoring reality too.
Linus
next prev parent reply other threads:[~2001-01-02 10:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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-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
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 12:05 dewar
2001-01-02 9:26 dewar
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=Pine.LNX.4.10.10101021032090.25012-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@racerx.synopsys.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).