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/109073] New: __builtin_vsx_lxvp() doesn't allow a const __vector_pair * operand in GCC 11 & 10 Date: Wed, 08 Mar 2023 22:32:48 +0000 [thread overview] Message-ID: <bug-109073-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109073 Bug ID: 109073 Summary: __builtin_vsx_lxvp() doesn't allow a const __vector_pair * operand in GCC 11 & 10 Product: gcc Version: 11.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bergner at gcc dot gnu.org Target Milestone: --- On GCC 11 and GCC 10, we error on the following test case which GCC 12 and trunk accept with no errors: bergner@ltcden2$ cat t.cc void foo (void *dst, const __vector_pair *src) { __vector_pair pair = __builtin_vsx_lxvp(0L, src); __builtin_vsx_disassemble_pair(dst, &pair); } bergner@ltcden2$ g++ -S -O2 -mcpu=power10 t.cc t.cc: In function ‘void foo(void*, const __vector_pair*)’: t.cc:4:47: error: invalid conversion from ‘const __vector_pair*’ to ‘__vector_pair*’ [-fpermissive] 4 | __vector_pair pair = __builtin_vsx_lxvp(0L, src); | ^~~ | | | const __vector_pair* <built-in>: note: initializing argument 2 of ‘__vector_pair __builtin_vsx_lxvp(sizetype, __vector_pair*)’ This was "fixed" in GCC 12 with Bill's rs6000 built-in rewrite, which we don't want to backport. I have a smaller fix which can be backported that I am testing. The same problem affects the __builtin_vsx_stxvp() and __builtin_vsx_disassemble_pair() and __builtin_mma_disassemble_acc() builtins.
next reply other threads:[~2023-03-08 22:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-08 22:32 bergner at gcc dot gnu.org [this message] 2023-03-08 22:34 ` [Bug target/109073] " bergner at gcc dot gnu.org 2023-05-29 10:08 ` jakub 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-109073-4@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).