From: Marek Polacek <polacek@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs] Add -Wmultistatement-macros
Date: Mon, 26 Jun 2017 14:54:00 -0000 [thread overview]
Message-ID: <20170626145432.GF4341@redhat.com> (raw)
I've committed the following to reflect the recent addition.
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.5
diff -u -r1.5 changes.html
--- changes.html 20 Jun 2017 10:19:11 -0000 1.5
+++ changes.html 26 Jun 2017 14:53:28 -0000
@@ -50,6 +50,14 @@
<h3 id="c-family">C family</h3>
<ul>
+ <li>New command-line options have been added for the C and C++ compilers:
+ <ul>
+ <li><code>-Wmultistatement-macros</code> warns about unsafe macros
+ expanding to multiple statements used as a body of a clause such
+ as <code>if</code>, <code>else</code>, <code>while</code>,
+ <code>switch</code>, or <code>for</code>.</li>
+ </ul>
+ </li>
<li><code>-fno-strict-overflow</code> is now mapped to
<code>-fwrapv</code> and signed integer overflow is now undefined by
default at all optimization levels. Using
Marek
reply other threads:[~2017-06-26 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170626145432.GF4341@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@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).