public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>,
	Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH v2] Handle OPAQUE_TYPE specially in verify_type [PR106833]
Date: Fri, 9 Sep 2022 19:56:42 -0500	[thread overview]
Message-ID: <0006b1a4-e5b4-f21d-da71-6aa7a74d8433@linux.ibm.com> (raw)
In-Reply-To: <b28b9125-32ce-20eb-94a8-0c4d47010080@linux.ibm.com>

On 9/9/22 8:27 AM, Kewen.Lin wrote:
> __attribute__((noipa))
> int foo(c){
>   return 0;
> }
> 
> int main ()
> {
>   const __vector_quad c;
>   int r = foo(c);
>   return r;
> }
> 
> Checking during LTO WPA, verify_type only gets type "const
> __vector_quad", no type "__vector_quad".
> 
> 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.

Peter


  reply	other threads:[~2022-09-10  0:56 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 [this message]
2022-09-10  1:47           ` Segher Boessenkool
2022-09-10  3:16             ` Peter Bergner

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=0006b1a4-e5b4-f21d-da71-6aa7a74d8433@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).