From: "Kewen.Lin" <linkw@linux.ibm.com>
To: richard.sandiford@arm.com
Cc: apinski@marvell.com, gcc-patches@gcc.gnu.org, polacek@redhat.com,
Joseph Myers <joseph@codesourcery.com>,
jason@redhat.com, nathan@acm.org,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] Fix aarch64 PR 99657: ICE with SVE types used without an error
Date: Wed, 7 Dec 2022 19:29:11 +0800 [thread overview]
Message-ID: <2c058aad-6863-6979-ce6f-116d63b940a5@linux.ibm.com> (raw)
In-Reply-To: <mpt7cz3a7zw.fsf@arm.com>
Hi Richard,
on 2022/12/7 17:16, Richard Sandiford wrote:
> "Kewen.Lin" <linkw@linux.ibm.com> writes:
>> Hi,
>>
>> In the recent discussion on how to make some built-in type only valid for
>> some target features efficiently[1], Andrew mentioned this patch which he
>> made previously (Thanks!). I confirmed it can help rs6000 related issue,
>> and noticed PR99657 is still opened, so I think we still want this to
>> be reviewed.
>
> But does it work for things like:
>
> void f(foo_t *x, foo_t *y) { *x = *y; }
>
> where no variables are being created with foo_t type?
>
I think it can work for this case as it touches build_indirect_ref.
> That's not to say we shouldn't have the patch. I'm just not sure
> it can be the complete solution.
I'm not sure about that either, maybe Andrew have more insights.
But as you pointed out in [1], I doubted trying to find all invalid
uses of a built-in type is worthwhile, it seems catching those usual
cases is enough and practical. So if this verify_type_context
framework can cover the most of uses, maybe it's a good direction
to go and extend.
[1] https://gcc.gnu.org/pipermail/gcc/2022-December/240218.html
BR,
Kewen
next prev parent reply other threads:[~2022-12-07 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 10:09 apinski
2021-11-09 14:38 ` Richard Sandiford
2022-12-07 2:21 ` Kewen.Lin
2022-12-07 9:16 ` Richard Sandiford
2022-12-07 11:29 ` Kewen.Lin [this message]
2022-12-07 12:55 ` Richard Sandiford
2022-12-08 2:14 ` Kewen.Lin
2022-12-08 7:43 ` Richard Sandiford
2022-12-08 9:15 ` Kewen.Lin
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=2c058aad-6863-6979-ce6f-116d63b940a5@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=apinski@marvell.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=nathan@acm.org \
--cc=polacek@redhat.com \
--cc=richard.sandiford@arm.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).