public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Jakub Jelinek <jakub@redhat.com>, Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [C++ PATCH] Avoid -Wreturn-type warnings if a switch has default label, no breaks inside of it, but is followed by a break (PR sanitizer/81275)
Date: Mon, 27 Nov 2017 13:39:00 -0000	[thread overview]
Message-ID: <553dc61a-6963-2d41-d55d-9b3fab8bd6f0@acm.org> (raw)
In-Reply-To: <20171126002256.GJ14653@tucnak>

On 11/25/2017 07:22 PM, Jakub Jelinek wrote:
> On Sat, Nov 25, 2017 at 10:01:22AM +0100, Jakub Jelinek wrote:
>> Actually, thinking about it some more, maybe it would be more efficient
>> to gather this information during construction of the SWITCH_STMT in some
>> new flag on the tree, so cxx_block_may_fallthru would just:
> 
> Here it is implemented, bootstrapped/regtested on x86_64-linux and
> i686-linux, ok for trunk?

nice.

> --- gcc/cp/cp-tree.h.jj	2017-11-17 08:40:32.000000000 +0100
> +++ gcc/cp/cp-tree.h	2017-11-25 21:25:48.277897180 +0100

> +/* Set if the body of a switch stmt contains a default: case label
> +   and does not contain any break; stmts, thus if SWITCH_STMT_BODY
> +   is not empty and doesn't fallthru, then the whole SWITCH_STMT
> +   can't fallthru either.  */
> +#define SWITCH_STMT_CANNOT_FALLTHRU_P(NODE) \
> +  TREE_LANG_FLAG_0 (SWITCH_STMT_CHECK (NODE))

The macro name isn't quite right.  As the comment says, it's not 
sufficient that this flag is set for the switch to not fall through -- 
the switch body must be non-empty (which I presume it cannot be as there 
must be a default label), and it cannot fall through in its own right.

The semantics of this flag are more like SWITCH_STMT_COVERS_ALL_CASES, 
perhaps something of that ilk would be a clearer name?

nathan

-- 
Nathan Sidwell

  reply	other threads:[~2017-11-27 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  0:37 Jakub Jelinek
2017-11-25 10:16 ` Jakub Jelinek
2017-11-26  9:05   ` Jakub Jelinek
2017-11-27 13:39     ` Nathan Sidwell [this message]
2017-11-27 14:10       ` Jakub Jelinek
2017-11-28  9:14         ` [C++ PATCH] Avoid -Wreturn-type warnings if a switch has default label, no breaks inside of it, but is followed by a break (PR sanitizer/81275, take 2) Jakub Jelinek
2017-11-28 11:58           ` Nathan Sidwell
2017-11-27 12:49   ` [C++ PATCH] Avoid -Wreturn-type warnings if a switch has default label, no breaks inside of it, but is followed by a break (PR sanitizer/81275) Nathan Sidwell
2017-11-27 12:44 ` Nathan Sidwell

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=553dc61a-6963-2d41-d55d-9b3fab8bd6f0@acm.org \
    --to=nathan@acm.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@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).