From: Jan Hubicka <hubicka@ucw.cz>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de, gdr@integrable-solutions.net
Subject: Re: Reorganize missing noreturn warning
Date: Wed, 09 Jun 2010 23:41:00 -0000 [thread overview]
Message-ID: <20100609225853.GB15748@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20100601004003.GB28772@kam.mff.cuni.cz>
> Hi,
> this patch moves noreturn warning code to same infrastructure as const/pure.
> This change wording of the warning by "might be possible candidat" to "might be
> candidate" and supress the warning when compiler can do full auto detection
> (i.e. for static functions, have patch for that in equeue).
>
> I added Wsuggest-attribute=noreturn and kept existing -Wmissing-noreturn as alias.
>
> Bootstrapped/regtested x86_64-linux, OK?
>
> Honza
>
> * doc/invoke.texi (Wsuggest-attribute): Document.
> (Wmissing-noreturn): Remove.
> * ipa-pure-const.c (warn_function_noreturn): New function.
> * opts.c (decode_options): Set warn_suggest_attribute_noreturn on
> warn_missing_noreturn.
> * common.opt (Wsuggest-attribute=noreturn): New.
> * tree-flow.h (warn_function_noreturn): Declare.
> * tree-cfg.c (execute_warn_function_noreturn): Use
> warn_function_noreturn.
> (gate_warn_function_noreturn): New.
> (pass_warn_function_noreturn): Update.
>
> * testsuite/gcc.dg/noreturn-7.c: Update.
> * testsuite/gcc.dg/noreturn-4.c: Update.
Ping...
next prev parent reply other threads:[~2010-06-09 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 0:40 Jan Hubicka
2010-06-09 23:41 ` Jan Hubicka [this message]
2010-06-10 3:53 ` Gabriel Dos Reis
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=20100609225853.GB15748@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=rguenther@suse.de \
/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).