From: Sylvestre Ledru <sylvestre@debian.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Jason Merrill <jason@redhat.com>
Subject: Re: [Patch] PR55189 enable -Wreturn-type by default
Date: Tue, 17 Jun 2014 17:37:00 -0000 [thread overview]
Message-ID: <53A07CCC.2030004@debian.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1406171712280.23412@digraph.polyomino.org.uk>
On 17/06/2014 19:15, Joseph S. Myers wrote:
> On Tue, 17 Jun 2014, Sylvestre Ledru wrote:
>
>> On 05/06/2014 20:01, Joseph S. Myers wrote:
>>>> Initially, I implemented -Wmissing-return to manage this case (
>>>> https://gcc.gnu.org/ml/gcc-patches/2014-01/msg00820.html ) but Jason
>>>> suggested to remove that:
>>>> https://gcc.gnu.org/ml/gcc-patches/2014-01/msg01033.html
>>>> (I don't have a strong opinion on the subject).
>>> I think splitting the option like that makes sense. Compatibility
>>> indicates that -Wreturn-type and -Wall should still enable
>>> -Wmissing-return, but only the other pieces of -Wreturn-type should be
>>> enabled by default, at least for C. (Enabling -Wimplicit-int by default
>>> might be a good starting point.)
>> OK.
>> As attachment, you will find a potential implementation. Is that what
>> you expect?
> It would help a lot if it included testcases for what various options /
> option combinations do / do not enable.
OK. I will do that.
We should test the following:
* default => run just -Wreturn-type
* -Wreturn-type => Run both
* -Wreturn-type + -Wmissing-return => Run both
* -Wno-return-type + -Wmissing-return => Run just the second one
* -Wno-return-type + -Wno-missing-return => Run none
Do you see any other?
> I expect that each option
> continues to enable the warnings it does at present (so if a user
> explicitly does -Wreturn-type it also enables the -Wmissing-return
> warnings, for example) - but some warnings would start to be enabled by
> default. If someone does e.g. -Wno-implicit that would disable the
> default -Wimplicit-int; if they do -Wno-implicit -Wimplicit that would
> have the same effect as just -Wimplicit (so keeping the default warnings
> enabled, and possibly enabling others).
>
OK. I will try to implement that later (I don't think -Wimplicit-int is
necessary to enable -Wreturn-type by default).
Besides that, are you OK with my changes? (with the tests updated)
Thanks,
Sylvestre
next prev parent reply other threads:[~2014-06-17 17:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 19:49 Sylvestre Ledru
2014-06-04 22:35 ` Mike Stump
2014-06-04 23:31 ` Joseph S. Myers
2014-06-05 9:33 ` Sylvestre Ledru
2014-06-05 18:01 ` Joseph S. Myers
2014-06-17 16:52 ` Sylvestre Ledru
2014-06-17 17:15 ` Joseph S. Myers
2014-06-17 17:37 ` Sylvestre Ledru [this message]
2014-06-17 17:41 ` Joseph S. Myers
2014-07-07 17:18 ` Sylvestre Ledru
2014-07-20 19:20 ` Sylvestre Ledru
2014-07-30 22:10 ` Joseph S. Myers
2014-08-11 7:44 ` Sylvestre Ledru
2014-08-12 17:49 ` Joseph S. Myers
2014-08-12 17:53 ` Sylvestre Ledru
2014-08-14 17:01 ` Sylvestre Ledru
-- strict thread matches above, loose matches on Subject: below --
2014-08-14 18:49 Manuel López-Ibáñez
2014-08-15 16:28 ` Sylvestre Ledru
2014-08-19 22:03 ` Joseph S. Myers
2014-08-20 21:42 ` Sylvestre Ledru
2014-08-20 21:58 ` Joseph S. Myers
2013-12-20 17:54 Sylvestre Ledru
2013-12-27 5:26 ` Chung-Ju Wu
2013-12-27 5:32 ` Yury Gribov
2014-01-14 17:49 ` Sylvestre Ledru
2014-01-16 19:44 ` Jason Merrill
2014-01-23 6:44 ` Sylvestre Ledru
2014-01-23 18:48 ` Jason Merrill
2014-01-23 18:57 ` Sylvestre Ledru
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=53A07CCC.2030004@debian.org \
--to=sylvestre@debian.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.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).