public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64554] using _mm_clmulepi64_si128 doesn't error with -O0
Date: Mon, 12 Jan 2015 09:41:00 -0000 [thread overview]
Message-ID: <bug-64554-4-r39HZksVT1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64554-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64554
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-01-12
CC| |hubicka at gcc dot gnu.org
Component|target |middle-end
Summary|_mm_clmulepi64_si128 |using _mm_clmulepi64_si128
|doesn't compile with -O2 |doesn't error with -O0
Ever confirmed|0 |1
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to charles from comment #5)
> No you're right.
>
> I could add, though, that the compiler should have said something.
>
> Also, why did it compile just fine with -O0?
Sounds like a bug (we should error immediately here IMHO). Probably
needs to annotate the CIF codes with whether this is "fatal" (won't
change with other inlining, IPA or LTO).
OTOH the headers are also poorly designed to trigger this kind of error.
Maybe we want to support __attribute__((always_inline("ISA not enabled")))
instead to be able to print a custom error message?
next prev parent reply other threads:[~2015-01-12 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 21:32 [Bug c/64554] New: _mm_clmulepi64_si128 doesn't compile with -O2 charles at kde dot org
2015-01-09 21:37 ` [Bug target/64554] " pinskia at gcc dot gnu.org
2015-01-09 21:43 ` charles at kde dot org
2015-01-09 21:53 ` jakub at gcc dot gnu.org
2015-01-09 21:55 ` charles at kde dot org
2015-01-12 9:41 ` rguenth at gcc dot gnu.org [this message]
2015-01-12 10:05 ` [Bug middle-end/64554] using _mm_clmulepi64_si128 doesn't error with -O0 jakub at gcc dot gnu.org
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=bug-64554-4-r39HZksVT1@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).