public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Trigraph warnings when compiling linux-2.4.0-prerelease1
Date: Tue, 02 Jan 2001 11:50:00 -0000	[thread overview]
Message-ID: <m2k88d7mwe.fsf@kelso.bothner.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101021103090.25012-100000@penguin.transmeta.com>

Linus Torvalds <torvalds@transmeta.com> writes:

>        -Wtrigraphs
>               Warn if any trigraphs are encountered (assuming they are enabled).
> 
> which certainly implies to me that even if you enabled "-Wtrigraphs", it
> wouldn't even't cause a warning if trigraphs aren't enabled (and again,
> it's documented that they are enabled by "-ansi" and by "-trigraphs" and
> disabled by default).

That is not my reading of the documentation, nor I think what it
intended to say. It clearly is silly that -Wtrigraphs would have no
effect if trigraphs are disabled - you might still want the warning to
catch cases of unintended trigraphs being miscompiled by other
compilers.

I read "assuming they are enabled" is a very poor way of saying "warn about
constructs that would be read as trigraphs if trigraphs were enabled."

(This question is of course separate from whether -Wtrigraphs should be
on by default or implied other switches like -Wall.  I think -Wtrigraphs
should definitely be implied by -Wall, though probably not default.)
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/

  reply	other threads:[~2001-01-02 11:50 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
2001-01-02 10:58       ` Joe Buck
2001-01-02 11:15         ` Linus Torvalds
2001-01-02 11:50           ` Per Bothner [this message]
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=m2k88d7mwe.fsf@kelso.bothner.com \
    --to=per@bothner.com \
    --cc=gcc@gcc.gnu.org \
    --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).