public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103661] __builtin_cpu_supports returns a negative integer for avx512vbmi2
Date: Thu, 16 Dec 2021 11:46:50 +0000 [thread overview]
Message-ID: <bug-103661-4-jLfyWY1mH1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103661-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103661
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:43d67e5e75627ad1f5ba2e983a730f37547ba9b7
commit r11-9394-g43d67e5e75627ad1f5ba2e983a730f37547ba9b7
Author: Martin Liska <mliska@suse.cz>
Date: Mon Dec 13 15:34:30 2021 +0100
i386: Fix emissing of __builtin_cpu_supports.
PR target/103661
gcc/ChangeLog:
* config/i386/i386-builtins.c (fold_builtin_cpu): Compare to 0
as API expects that non-zero values are returned (do that
it mask == 31).
For "avx512vbmi2" argument, we return now 1 << 31, which is a
negative integer value.
(cherry picked from commit 127c7178d5ec502d95862fd823537cbca1a0cb99)
next prev parent reply other threads:[~2021-12-16 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 16:56 [Bug target/103661] New: " stefan.kneifel at bluewin dot ch
2021-12-11 18:08 ` [Bug target/103661] " pinskia at gcc dot gnu.org
2021-12-11 18:08 ` pinskia at gcc dot gnu.org
2021-12-11 23:50 ` stefan.kneifel at bluewin dot ch
2021-12-12 12:50 ` stefan.kneifel at bluewin dot ch
2021-12-13 10:12 ` marxin at gcc dot gnu.org
2021-12-15 9:31 ` cvs-commit at gcc dot gnu.org
2021-12-15 10:52 ` marxin at gcc dot gnu.org
2021-12-15 10:52 ` marxin at gcc dot gnu.org
2021-12-16 11:46 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-16 13:03 ` cvs-commit at gcc dot gnu.org
2021-12-16 13:04 ` marxin 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-103661-4-jLfyWY1mH1@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).