From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26077 invoked by alias); 12 Jan 2015 09:41:11 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 26023 invoked by uid 48); 12 Jan 2015 09:41:07 -0000 From: "rguenth at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc component short_desc everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg00764.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64554 Richard Biener 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 --- (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?