From: Marek Polacek <polacek@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: PATCH to add more FALLTHRU markers
Date: Tue, 27 Sep 2016 19:22:00 -0000 [thread overview]
Message-ID: <20160927191847.GJ3223@redhat.com> (raw)
In-Reply-To: <87bmz9xj7w.fsf@mid.deneb.enyo.de>
On Tue, Sep 27, 2016 at 08:58:59PM +0200, Florian Weimer wrote:
> * Marek Polacek:
>
> > @@ -11498,21 +11508,23 @@
> > case V64QImode:
> > case V32HImode:
> > if (TARGET_AVX512F)
> > - {
> > - tmp = "p<logic>";
> > - ssesuffix = "q";
> > - break;
> > - }
> > + {
> > + tmp = "p<logic>";
> > + ssesuffix = "q";
> > + break;
> > + }
> > + /* FALLTHRU */
> > case V32QImode:
> > case V16HImode:
> > case V16QImode:
> > case V8HImode:
> > if (TARGET_AVX512VL || TARGET_AVX2 || TARGET_SSE2)
> > - {
> > - tmp = "p<logic>";
> > - ssesuffix = TARGET_AVX512VL ? "q" : "";
> > - break;
> > - }
> > + {
> > + tmp = "p<logic>";
> > + ssesuffix = TARGET_AVX512VL ? "q" : "";
> > + break;
> > + }
> > + /* FALLTHRU */
> > default:
> > gcc_unreachable ();
> > }
>
> Why isn't this a bug? Wouldn't we want to reach gcc_unreachable ()
> if, for example !TARGET_AVX512F and TARGET_SSE2?
?? In that case the FALLTHRU should be there if it's intentional that
we may fall through to default. Otherwise not sure what you mean.
Marek
next prev parent reply other threads:[~2016-09-27 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:55 Marek Polacek
2016-09-27 19:00 ` Richard Sandiford
2016-09-29 17:22 ` Marek Polacek
2016-09-27 19:08 ` Florian Weimer
2016-09-27 19:22 ` Marek Polacek [this message]
2016-09-27 19:33 ` Florian Weimer
2016-09-27 19:39 ` Marek Polacek
2016-09-27 20:13 ` Jakub Jelinek
2016-09-29 17:17 ` Marek Polacek
2016-09-29 20:21 ` Jakub Jelinek
2016-09-30 21:31 ` [PATCH] FALLTHRU markers for sse.md and some cleanups Jakub Jelinek
2016-10-01 8:31 ` Uros Bizjak
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=20160927191847.GJ3223@redhat.com \
--to=polacek@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).