public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111645] Intrinsics vec_sldb /vec_srdb fail with __vector unsigned __int128 Date: Sat, 30 Sep 2023 15:53:49 +0000 [thread overview] Message-ID: <bug-111645-4-mwX0hphfor@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111645-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111645 Peter Bergner <bergner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2023-09-30 CC| |bergner at gcc dot gnu.org, | |dje at gcc dot gnu.org, | |linkw at gcc dot gnu.org, | |meissner at gcc dot gnu.org, | |segher at gcc dot gnu.org --- Comment #1 from Peter Bergner <bergner at gcc dot gnu.org> --- I see that we have created built-in overloads for signed and unsigned vector char through vector long long. That said, the rs6000-builtins.def only seems to support the signed vector types though, which is why you're seeing an error. So confirmed. That said, I believe your 3rd argument needs to be a real constant integer, since the vsldbi instruction requires that. It doesn't allow for a const int variable. I notice some older (not trunk) gcc versions are ICEing with that, so another bug to look at. I do not see any documentation that says we support the vector __int128 type. Where exactly did you see that? However, from the instruction description, it seems like the hw instruction could support that.
next prev parent reply other threads:[~2023-09-30 15:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-29 23:06 [Bug target/111645] New: " munroesj at gcc dot gnu.org 2023-09-30 15:53 ` bergner at gcc dot gnu.org [this message] 2023-09-30 19:43 ` [Bug target/111645] " munroesj at gcc dot gnu.org 2023-09-30 19:46 ` munroesj at gcc dot gnu.org 2023-10-01 20:09 ` munroesj at gcc dot gnu.org 2023-10-19 19:36 ` carll at gcc dot gnu.org 2023-10-25 16:46 ` munroesj 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-111645-4-mwX0hphfor@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: linkBe 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).