public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/15378] [3.3/3.4/3.5 regression] -Werror should provide notification of why gcc is exiting Date: Wed, 12 May 2004 15:14:00 -0000 [thread overview] Message-ID: <20040511181128.12178.qmail@sourceware.org> (raw) In-Reply-To: <20040511170322.15378.ed@catmur.co.uk> ------- Additional Comments From bangerth at dealii dot org 2004-05-11 18:11 ------- Hm, I'm not exactly sure what you mean -- if you give -Werror to the compiler, then shouldn't you expect the compiler to stop when it encounters an error? If your Makefiles are written such that they don't show the actual commmand line of the compiler invokation, this can hardly count as a bug in gcc. That being said, we indeed have a regression: ---------- main () {} ---------- yields g/x> /home/bangerth/bin/gcc-2.95.3/bin/c++ x.cc -Wall -W -Werror cc1plus: warnings being treated as errors x.cc:1: warning: ANSI C++ forbids declaration `main' with no type g/x> /home/bangerth/bin/gcc-3.2.3/bin/c++ x.cc -Wall -W -Werror cc1plus: warnings being treated as errors x.cc:1: warning: ISO C++ forbids declaration of `main' with no type g/x> /home/bangerth/bin/gcc-3.3.4-pre/bin/c++ x.cc -Wall -W -Werror x.cc:1: warning: ISO C++ forbids declaration of `main' with no type g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ x.cc -Wall -W -Werror x.cc:1: warning: ISO C++ forbids declaration of `main' with no type g/x> /home/bangerth/bin/gcc-3.5-pre/bin/c++ x.cc -Wall -W -Werror x.cc:1: warning: ISO C++ forbids declaration of `main' with no type In other words, the indication of -Werror was dropped sometime between 3.2.x and 3.3.x. W. -- What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |minor Known to fail| |3.3.4 3.4.0 3.5.0 Known to work| |2.95.3 3.2.3 Summary|-Werror should provide |[3.3/3.4/3.5 regression] - |notification of why gcc is |Werror should provide |exiting |notification of why gcc is | |exiting Target Milestone|--- |3.3.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15378
next prev parent reply other threads:[~2004-05-11 18:11 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-12 13:13 [Bug other/15378] New: " ed at catmur dot co dot uk 2004-05-12 13:41 ` [Bug other/15378] " pinskia at gcc dot gnu dot org 2004-05-12 14:33 ` jsm at polyomino dot org dot uk 2004-05-12 15:14 ` bangerth at dealii dot org [this message] 2004-06-06 3:57 ` [Bug other/15378] [3.3/3.4/3.5 regression] " giovannibajo at libero dot it 2004-06-12 22:07 ` mmitchel at gcc dot gnu dot org 2004-06-22 8:05 ` mmitchel at gcc dot gnu dot org 2004-08-19 21:13 ` mmitchel at gcc dot gnu dot org 2004-08-19 21:33 ` gdr at integrable-solutions dot net 2004-08-29 19:09 ` mmitchel at gcc dot gnu dot org 2004-08-30 4:56 ` gdr at gcc dot gnu dot org 2004-11-01 0:47 ` [Bug other/15378] [3.3/3.4 " mmitchel at gcc dot gnu dot org 2005-05-19 17:37 ` mmitchel at gcc dot gnu dot 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=20040511181128.12178.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: linkBe 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).