public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Simon.Richter at hogyros dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52347] -Wno-tabs -Wall -Wno-tabs still warns about tabs Date: Fri, 14 Jun 2013 19:43:00 -0000 [thread overview] Message-ID: <bug-52347-4-23Yn2nb5AX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52347-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52347 Simon Richter <Simon.Richter at hogyros dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Simon.Richter at hogyros dot de --- Comment #2 from Simon Richter <Simon.Richter at hogyros dot de> --- In 4.8, this causes build failures for me: $ g++ -g -Wall -W -Werror -Wno-unused -I. -o stage1/tree_bison_lex.o -c tree_bison_lex.cpp tree_bison_lex.cpp:1744:13: error: unused parameter 'yyscanner' [-Werror=unused-parameter] As can be guessed from the name, this is a file that is generated from flex, which is why I've added -Wno-unused for this file specifically. 4.7 did not warn.
next prev parent reply other threads:[~2013-06-14 19:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-23 8:37 [Bug fortran/52347] New: " burnus at gcc dot gnu.org 2012-02-23 8:42 ` [Bug fortran/52347] " manu at gcc dot gnu.org 2013-06-14 19:43 ` Simon.Richter at hogyros dot de [this message] 2013-06-14 21:27 ` manu at gcc dot gnu.org 2013-06-14 23:15 ` Simon.Richter at hogyros dot de 2013-06-15 9:36 ` manu at gcc dot gnu.org 2014-12-11 17:41 ` burnus 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=bug-52347-4-23Yn2nb5AX@http.gcc.gnu.org/bugzilla/ \ --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).