public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH to fix bogus -Wimplicit-fallthrough warning (PR c++/77803)
Date: Fri, 07 Oct 2016 09:39:00 -0000	[thread overview]
Message-ID: <20161007093937.GE7282@tucnak.redhat.com> (raw)
In-Reply-To: <20161007084518.GC3223@redhat.com>

On Fri, Oct 07, 2016 at 10:45:18AM +0200, Marek Polacek wrote:
> Ping.
> 
> On Sat, Oct 01, 2016 at 04:17:22PM +0200, Marek Polacek wrote:
> > On Sat, Oct 01, 2016 at 07:17:50AM +0200, Markus Trippelsdorf wrote:
> > > On 2016.09.30 at 23:31 +0200, Marek Polacek wrote:
> > > > This PR reports a bogus -Wimplicit-fallthrough warning on the attached test.
> > > > The problem is that last_stmt_in_scope should for GIMPLE_TRY, if the last
> > > > statement of the eval part can't fallthrough, return this statement and don't
> > > > warn.  And the same should be true for FALLTHROUGH ().   This patch fixes it.
> > > > 
> > > > Bootstrapped/regtested on x86_64-linux, ok for trunk?
> > > 
> > > Try to compile the testcase without the fallthrough attribute...
> > 
> > Nuts.  Forgot that gimple_call_internal_p doesn't handle NULL.
> > 
> > Bootstrapped/regtested on x86_64-linux and ppc64-linux, ok for trunk?
> > 
> > 2016-10-01  Marek Polacek  <polacek@redhat.com>
> > 
> > 	PR c++/77803
> > 	* gimplify.c (last_stmt_in_scope): Add check for FALLTHROUGH ().
> > 
> > 	* g++.dg/warn/Wimplicit-fallthrough-1.C: New test.

Ok, thanks.

	Jakub

      reply	other threads:[~2016-10-07  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 21:39 Marek Polacek
2016-10-01  5:18 ` Markus Trippelsdorf
2016-10-01 14:42   ` Marek Polacek
2016-10-02 18:42     ` Jason Merrill
2016-10-02 21:57       ` Jakub Jelinek
2016-10-07  8:45     ` Marek Polacek
2016-10-07  9:39       ` Jakub Jelinek [this message]

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=20161007093937.GE7282@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=polacek@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).