public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106017] [PowerPC] No array-to-pointer conversion for MMA accumulator
Date: Fri, 17 Jun 2022 17:35:29 +0000	[thread overview]
Message-ID: <bug-106017-4-SwbLCiVA9a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106017-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106017

--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #2)
> We do not want or allow automatic conversions between the opaque
> __vector_pair and __vector_quad types and other types and those are
> correctly disallowed there.

Of course, but that is not what this is about...

> As for the pointer conversions tested there, I guess they came along for the
> ride?  Nemanja, do you remember the history there?  Or does LLVM allow the
> pointer conversions and it's just GCC that complains?

... this is.

Possibly the restriction prevents some ICEs elsewhere, but those just need to
be solved then, not hidden.

  parent reply	other threads:[~2022-06-17 17:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 14:34 [Bug c/106017] New: " nemanja.i.ibm at gmail dot com
2022-06-17 17:16 ` [Bug target/106017] " segher at gcc dot gnu.org
2022-06-17 17:31 ` bergner at gcc dot gnu.org
2022-06-17 17:35 ` segher at gcc dot gnu.org [this message]
2022-06-17 19:19 ` nemanja.i.ibm at gmail dot com
2022-06-17 19:51 ` segher at gcc dot gnu.org
2022-06-17 20:50 ` segher at gcc dot gnu.org
2022-06-17 22:23 ` bergner at gcc dot gnu.org
2022-08-27 17:28 ` bergner at gcc dot gnu.org
2022-08-27 17:30 ` bergner at gcc dot gnu.org
2022-08-27 18:27 ` bergner at gcc dot gnu.org
2022-08-28  0:44 ` cvs-commit at gcc dot gnu.org
2022-08-29 22:38 ` cvs-commit at gcc dot gnu.org
2022-08-30  0:22 ` cvs-commit at gcc dot gnu.org
2022-08-30  1:13 ` cvs-commit at gcc dot gnu.org
2022-08-30  1:14 ` bergner 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-106017-4-SwbLCiVA9a@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).