From: Joe Buck <jbuck@racerx.synopsys.com>
To: fjh@cs.mu.oz.au (Fergus Henderson)
Cc: dewar@gnat.com, torvalds@transmeta.com, gcc@gcc.gnu.org, per@bothner.com
Subject: Re: Trigraph warnings when compiling linux-2.4.0-prerelease1
Date: Wed, 03 Jan 2001 11:21:00 -0000 [thread overview]
Message-ID: <200101031920.LAA04469@racerx.synopsys.com> (raw)
In-Reply-To: <20010103140307.B4402@hg.cs.mu.oz.au>
On 02-Jan-2001, dewar@gnat.com <dewar@gnat.com> wrote:
> > In fact the current documentation is clear and appears to match the
> > documentation.
Fergus Henderson writes:
> I'm not quite sure what you mean there (did you intend to say
> "appears to match the implementation"?).
>
> The current documentation says
>
> `-Wtrigraphs'
> Warn if any trigraphs are encountered that might change the
> meaning of the program (trigraphs within comments are not warned
> about).
>
> which is different to the documentation quoted earlier in this
> thread. I agree that it seems clear enough.
Linus was talking about the documentation for the most recently
released compiler (the manual shipped with 2.95.2), not the manual
in the snapshots.
(This is just for clarification, I'm not going to continue the argument).
next prev parent reply other threads:[~2001-01-03 11:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 12:05 dewar
2001-01-02 9:26 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=200101031920.LAA04469@racerx.synopsys.com \
--to=jbuck@racerx.synopsys.com \
--cc=dewar@gnat.com \
--cc=fjh@cs.mu.oz.au \
--cc=gcc@gcc.gnu.org \
--cc=per@bothner.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).