public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/57624] New: BZHI instrinsic is missing
@ 2013-06-15 14:33 sgunderson at bigfoot dot com
2013-06-15 16:04 ` [Bug target/57624] " jakub at gcc dot gnu.org
2013-06-27 11:23 ` sgunderson at bigfoot dot com
0 siblings, 2 replies; 3+ messages in thread
From: sgunderson at bigfoot dot com @ 2013-06-15 14:33 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3798 bytes --]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57624
Bug ID: 57624
Summary: BZHI instrinsic is missing
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: sgunderson at bigfoot dot com
Hi,
The GCC documentation
(http://gcc.gnu.org/onlinedocs/gcc/X86-Built_002din-Functions.html) claims
there should be such an intrinsic, added in gcc 4.7:
unsigned long long _bzhi_u64 (unsigned long long, unsigned long long)
Yet, with gcc 4.8.1 (Debian 4.8.1-2), nothing of the sort exists:
sesse@gruessi:~$ gcc-4.8 -Wall -O2 -mbmi2 -c bzhi-test.c
bzhi-test.c: In function âfuncâ:
bzhi-test.c:5:2: warning: implicit declaration of function â_bzhi_u64â
[-Wimplicit-function-declaration]
return _bzhi_u64(x, y);
^
A function call is generated instead, which was obviously not what I intended.
:-)
I thought this was maybe just a documentation error, but
__builtin_ia32_bzhi_u64 also does not exist.
>From gcc-bugs-return-424417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jun 15 15:51:30 2013
Return-Path: <gcc-bugs-return-424417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26542 invoked by alias); 15 Jun 2013 15:51:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26497 invoked by uid 48); 15 Jun 2013 15:51:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/57620] Phantom terminator confuses raw string literal parsing.
Date: Sat, 15 Jun 2013 15:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to attachments.created
Message-ID: <bug-57620-4-75siW6s7I8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57620-4@http.gcc.gnu.org/bugzilla/>
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: 2013-06/txt/msg00796.txt.bz2
Content-length: 834
http://gcc.gnu.org/bugzilla/show_bug.cgi?idW620
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 30306
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id0306&actioníit
gcc49-pr57620.patch
So far only very lightly tested patch, passes raw-string* tests (except for
raw-string-2.c which contains also trigraph tests that were valid in the
earlier raw string paper, but aren't valid in C++11) and this plus a few other
tests.
Will still need to adjust raw-string-2.c, and add sufficient test coverage for
all the corner cases.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/57624] BZHI instrinsic is missing
2013-06-15 14:33 [Bug target/57624] New: BZHI instrinsic is missing sgunderson at bigfoot dot com
@ 2013-06-15 16:04 ` jakub at gcc dot gnu.org
2013-06-27 11:23 ` sgunderson at bigfoot dot com
1 sibling, 0 replies; 3+ messages in thread
From: jakub at gcc dot gnu.org @ 2013-06-15 16:04 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57624
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If you forget to include
#include <x86intrin.h>
then don't be surprised.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/57624] BZHI instrinsic is missing
2013-06-15 14:33 [Bug target/57624] New: BZHI instrinsic is missing sgunderson at bigfoot dot com
2013-06-15 16:04 ` [Bug target/57624] " jakub at gcc dot gnu.org
@ 2013-06-27 11:23 ` sgunderson at bigfoot dot com
1 sibling, 0 replies; 3+ messages in thread
From: sgunderson at bigfoot dot com @ 2013-06-27 11:23 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57624
--- Comment #2 from sgunderson at bigfoot dot com ---
Shouldn't really the documentation say so, then? The entire GCC manual seems to
make no note of this header at all, as far as I can see.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-06-27 11:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-15 14:33 [Bug target/57624] New: BZHI instrinsic is missing sgunderson at bigfoot dot com
2013-06-15 16:04 ` [Bug target/57624] " jakub at gcc dot gnu.org
2013-06-27 11:23 ` sgunderson at bigfoot dot com
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).