public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95082] LE implementations of vec_cnttz_lsbb and vec_cntlz_lsbb are wrong
Date: Wed, 23 Feb 2022 20:25:52 +0000 [thread overview]
Message-ID: <bug-95082-4-55rEgm0iN9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95082-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95082
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|11.0 |
Summary|[11] LE implementations of |LE implementations of
|vec_cnttz_lsbb and |vec_cnttz_lsbb and
|vec_cntlz_lsbb are wrong |vec_cntlz_lsbb are wrong
--- Comment #10 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
>From some private discussion today, this goes back quite some ways, and we're
simply going to document this as a change in behavior. The old behavior was
wrong and usage of these built-ins is not very prevalent. We'll make a point
of this change in the release notes, rather than do any backports.
prev parent reply other threads:[~2022-02-23 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 13:34 [Bug target/95082] New: " wschmidt at gcc dot gnu.org
2020-05-12 13:34 ` [Bug target/95082] " wschmidt at gcc dot gnu.org
2020-05-15 0:53 ` pc at us dot ibm.com
2020-05-15 10:50 ` segher at gcc dot gnu.org
2020-05-15 10:51 ` segher at gcc dot gnu.org
2021-04-27 11:38 ` jakub at gcc dot gnu.org
2021-07-28 7:04 ` rguenth at gcc dot gnu.org
2022-01-18 15:15 ` wschmidt at gcc dot gnu.org
2022-02-03 17:17 ` [Bug target/95082] [11/12] " cvs-commit at gcc dot gnu.org
2022-02-11 13:59 ` [Bug target/95082] [11] " wschmidt at gcc dot gnu.org
2022-02-11 15:15 ` segher at gcc dot gnu.org
2022-02-23 20:25 ` wschmidt at gcc dot gnu.org [this message]
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-95082-4-55rEgm0iN9@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).