public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37187] please provide a way to treat -pedantic as warning when using -Werror
Date: Thu, 21 Aug 2008 18:05:00 -0000	[thread overview]
Message-ID: <20080821180428.11516.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37187-15165@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from manu at gcc dot gnu dot org  2008-08-21 18:04 -------
There are several bugs here:

1) -Wno-error=pendatic does not work. But neither does -Werror=pedantic or
-no-pedantic, so this is a feature request. We would need to implement
-Wpedantic as a synonym of -pedantic. I have been thinking about doing this for
a while anyway just for consistency. However, -pedantic-errors is not
equivalent to -Werror=pedantic, so not sure in which direction should the
inconsistency be solved.

2) The duplicated messages. This seems hard to fix: too many jumps around, too
many global variables being used...

x.c:10: warning: initializer element is not computable at load time
x.c:10: warning: initializer element is not computable at load time

3) -fdiagnostics-show-option does not show [-pedantic]. This is easy to fix.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37187


  parent reply	other threads:[~2008-08-21 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 13:26 [Bug c/37187] New: " edwintorok at gmail dot com
2008-08-21 13:28 ` [Bug c/37187] " edwintorok at gmail dot com
2008-08-21 16:13 ` manu at gcc dot gnu dot org
2008-08-21 18:05 ` manu at gcc dot gnu dot org [this message]
2008-08-22 12:17 ` manu at gcc dot gnu dot org
     [not found] <bug-37187-4@http.gcc.gnu.org/bugzilla/>
2011-11-18 20:11 ` skunk at iskunk dot org
2012-04-22 20:03 ` manu at gcc dot gnu.org
2021-07-29 17:26 ` pinskia at gcc dot gnu.org

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=20080821180428.11516.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).