From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Jeff Law <law@redhat.com>, Jason Merrill <jason@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [PATCH, updated] Add a warning for suspicious use of conditional expressions in boolean context
Date: Thu, 15 Sep 2016 16:51:00 -0000 [thread overview]
Message-ID: <HE1PR0701MB21691C0679AB934696F0C13DE4F00@HE1PR0701MB2169.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <89a3e9db-e47c-57a3-70bb-62cd8c783c0c@redhat.com>
On 09/15/16 18:23, Jeff Law wrote:
> On 09/15/2016 10:00 AM, Bernd Edlinger wrote:
>> On 09/15/16 17:44, Jeff Law wrote:
>>> On 09/14/2016 12:11 PM, Jason Merrill wrote:
>>>>
>>>> I think we could have both, where the weaker form is part of -Wall and
>>>> people can explicitly select the stronger form.
>>> That's been a fairly standard way to handle this kind of thing. It
>>> works for me.
>>>
>>> Jeff
>>
>> The warning could for instance be more aggressive when -pedantic is in
>> effect?
> I wouldn't do it on -pedantic. We've usually used levels or -Wfoo
> -Wfoo-bar kinds of schemes.
It would be kind of good to enable the extended warning level on
the gcc bootstrap, where we have -Wall and -pedantic and more.
So level 1 could be enabled with -Wall and level 2 could be enabled
with -pedantic and/or -Wpedantic.
Bernd.
next prev parent reply other threads:[~2016-09-15 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 18:53 [PATCH] " Bernd Edlinger
2016-09-04 8:45 ` [PATCHv2] " Bernd Edlinger
2016-09-05 11:41 ` Joseph Myers
2016-09-05 14:59 ` Bernd Edlinger
2016-09-05 16:57 ` Joseph Myers
[not found] ` <CAPWdEev7VW5LT47iPh-0EgAJz5ELEnoZ_snLtg-F5ZR+etLimg@mail.gmail.com>
2016-09-05 20:03 ` Bernd Edlinger
2016-09-12 19:40 ` [PATCH] " Jeff Law
2016-09-12 20:02 ` Bernd Edlinger
2016-09-12 20:18 ` Jeff Law
2016-09-12 21:28 ` Bernd Edlinger
2016-09-14 16:14 ` [PATCH, updated] " Bernd Edlinger
2016-09-14 16:50 ` Jason Merrill
2016-09-14 17:41 ` Bernd Edlinger
2016-09-14 19:04 ` Jason Merrill
[not found] ` <AM4PR0701MB2162B5B8246F8A10B4B6E42CE4F10@AM4PR0701MB2162.eurprd07.prod.outlook.com>
2016-09-14 20:17 ` [PATCHv3] " Bernd Edlinger
2016-09-15 15:52 ` [PATCH, updated] " Jeff Law
2016-09-15 16:20 ` Bernd Edlinger
2016-09-15 16:36 ` Jeff Law
2016-09-15 16:51 ` Bernd Edlinger [this message]
2016-09-15 19:21 ` Joseph Myers
2016-09-15 20:34 ` Jason Merrill
2016-09-15 20:45 ` Bernd Edlinger
2016-09-14 17:54 ` Steve Kargl
2016-09-14 17:56 ` Bernd Edlinger
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=HE1PR0701MB21691C0679AB934696F0C13DE4F00@HE1PR0701MB2169.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
/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).