public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simb611alt at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101985] vec_cpsgn parameter order
Date: Wed, 29 Sep 2021 19:33:20 +0000 [thread overview]
Message-ID: <bug-101985-4-ERBDuz1Byh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101985-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101985
--- Comment #4 from Kunwar Maheep Singh <simb611alt at gmail dot com> ---
(In reply to Bill Schmidt from comment #3)
> Kunwar, can you please tell us (if you don't mind) where the problem was
> detected? Since we're changing behavior of the intrinsic, we'll need to
> document this, and knowing whether we have problematic code in the wild that
> relies on present behavior would be helpful.
I detected it in SIMDe (https://github.com/simd-everywhere/simde).
Relevant commit -
https://github.com/simd-everywhere/simde/commit/1ba15969fdc1b302c0e50084420412368a14cd96
next prev parent reply other threads:[~2021-09-29 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 18:36 [Bug c/101985] New: " simb611alt at gmail dot com
2021-09-23 16:40 ` [Bug target/101985] " wschmidt at gcc dot gnu.org
2021-09-24 15:33 ` wschmidt at gcc dot gnu.org
2021-09-28 15:28 ` wschmidt at gcc dot gnu.org
2021-09-29 19:33 ` simb611alt at gmail dot com [this message]
2021-10-12 22:39 ` cvs-commit at gcc dot gnu.org
2021-10-12 22:43 ` wschmidt at gcc dot gnu.org
2021-11-23 21:26 ` cvs-commit at gcc dot gnu.org
2021-11-23 22:40 ` cvs-commit at gcc dot gnu.org
2021-11-23 23:06 ` cvs-commit at gcc dot gnu.org
2021-11-23 23:07 ` wschmidt at gcc dot gnu.org
2022-11-17 21:02 ` mark.j.abraham at gmail dot com
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-101985-4-ERBDuz1Byh@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).