public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "Kewen.Lin" <linkw@linux.ibm.com>,
	Richard Biener <richard.guenther@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] Handle OPAQUE_TYPE specially in verify_type [PR106833]
Date: Fri, 9 Sep 2022 22:16:18 -0500	[thread overview]
Message-ID: <d7edb825-bef3-9b7f-4998-c4787fa61f0b@linux.ibm.com> (raw)
In-Reply-To: <20220910014713.GT25951@gate.crashing.org>

On 9/9/22 8:47 PM, Segher Boessenkool wrote:
> On Fri, Sep 09, 2022 at 07:56:42PM -0500, Peter Bergner wrote:
>> On 9/9/22 8:27 AM, Kewen.Lin wrote:
>>> btw, it needs some hacking in rs6000_function_arg to make this
>>> opaque type valid for function arg.
>>
>> We don't allow (at this time) __vector_pair or __vector_quad to be
>> used as actual arguments to non-builtin functions.  We do allow
>> pointers to those types though.
> 
> It would be nice to support that, if it isn't too hard.  It won't be
> digging us into a hole, experience has taught us :-)

Sure, but we didn't need it at the time (and still don't) and if we do
add support for that, we'll have to update the ABIs to describe how
they are passed and returned and that is no small feat in itself.
It's just a fair amount of work when no one is actually asking for
that support and we have a lot of other things to work on.

Peter




      reply	other threads:[~2022-09-10  3:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  5:53 [PATCH] " Kewen.Lin
2022-09-08  7:36 ` Richard Biener
2022-09-09  6:51   ` [PATCH v2] " Kewen.Lin
2022-09-09  7:25     ` Richard Biener
2022-09-09 13:27       ` Kewen.Lin
2022-09-10  0:56         ` Peter Bergner
2022-09-10  1:47           ` Segher Boessenkool
2022-09-10  3:16             ` Peter Bergner [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=d7edb825-bef3-9b7f-4998-c4787fa61f0b@linux.ibm.com \
    --to=bergner@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@linux.ibm.com \
    --cc=richard.guenther@gmail.com \
    --cc=segher@kernel.crashing.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).