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 middle-end/7651] Define -Wextra strictly in terms of other warning flags Date: Sat, 16 Dec 2006 16:48:00 -0000 [thread overview] Message-ID: <20061216164816.28358.qmail@sourceware.org> (raw) In-Reply-To: <bug-7651-1366@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from manu at gcc dot gnu dot org 2006-12-16 16:48 ------- Subject: Bug 7651 Author: manu Date: Sat Dec 16 16:48:01 2006 New Revision: 119963 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119963 Log: 2006-12-16 Manuel Lopez-Ibanez <manu@gcc.gnu.org> PR middle-end/7651 * c.opt (Wempty-body): New. * doc/invoke.texi (Wempty-body): Document it. (Wextra): Enabled by -Wextra. * c-opts.c (c_common_post_options): Enabled by -Wextra. * c-common.c (empty_body_warning): Replace Wextra with Wempty-body. * c-parser.c (c_parser_c99_block_statement): Likewise. testsuite/ * gcc.dg/20001116-1.c: Replace -Wextra with -Wempty-body. * gcc.dg/if-empty-1.c: Likewise. * gcc.dg/pr23165.c: Likewise. * g++.dg/warn/empty-body.C: Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/c-common.c trunk/gcc/c-opts.c trunk/gcc/c-parser.c trunk/gcc/c.opt trunk/gcc/doc/invoke.texi trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/warn/empty-body.C trunk/gcc/testsuite/gcc.dg/20001116-1.c trunk/gcc/testsuite/gcc.dg/if-empty-1.c trunk/gcc/testsuite/gcc.dg/pr23165.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7651
next prev parent reply other threads:[~2006-12-16 16:48 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-7651-1366@http.gcc.gnu.org/bugzilla/> 2006-08-28 20:33 ` pinskia at gcc dot gnu dot org 2006-12-15 12:35 ` patchapp at dberlin dot org 2006-12-16 16:48 ` manu at gcc dot gnu dot org [this message] 2006-12-18 0:20 ` patchapp at dberlin dot org 2006-12-20 0:57 ` patchapp at dberlin dot org 2006-12-22 15:54 ` manu at gcc dot gnu dot org 2006-12-23 17:45 ` manu at gcc dot gnu dot org 2006-12-24 14:15 ` patchapp at dberlin dot org 2006-12-24 14:30 ` patchapp at dberlin dot org 2006-12-29 18:35 ` patchapp at dberlin dot org 2006-12-29 19:30 ` patchapp at dberlin dot org 2007-01-02 17:33 ` manu at gcc dot gnu dot org 2007-01-05 23:40 ` patchapp at dberlin dot org 2007-01-07 12:56 ` patchapp at dberlin dot org 2007-01-07 21:05 ` patchapp at dberlin dot org 2007-01-08 21:25 ` patchapp at dberlin dot org 2007-01-16 0:57 ` patchapp at dberlin dot org 2007-01-23 19:45 ` patchapp at dberlin dot org 2007-02-12 9:32 ` manu at gcc dot gnu dot org 2007-02-12 22:10 ` patchapp at dberlin dot org 2007-05-20 0:46 ` manu at gcc dot gnu dot org 2007-05-20 20:34 ` manu at gcc dot gnu dot org 2008-08-08 23:35 ` manu at gcc dot gnu dot org [not found] <bug-7651-4@http.gcc.gnu.org/bugzilla/> 2014-08-21 7:05 ` mpolacek at gcc dot gnu.org 2014-08-21 9:02 ` manu at gcc dot gnu.org 2014-11-11 8:18 ` mpolacek at gcc dot gnu.org 2015-04-22 11:59 ` jakub at gcc dot gnu.org 2015-07-16 9:16 ` rguenth 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=20061216164816.28358.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).