From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: pinskia@gmail.com
Subject: Re: [PATCH] Prevent TYPE_PRECISION on VECTOR_TYPEs
Date: Fri, 9 Jun 2023 11:53:07 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2306091151570.4723@jbgna.fhfr.qr> (raw)
In-Reply-To: <q75n3484-1q40-q314-3nr-4n1psr635635@fhfr.qr>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Fri, 9 Jun 2023, Richard Biener wrote:
> On Fri, 9 Jun 2023, Richard Biener wrote:
>
> > The following makes sure that using TYPE_PRECISION on VECTOR_TYPE
> > ICEs when tree checking is enabled. This should avoid wrong-code
> > in cases like PR110182 and instead ICE.
> >
> > Bootstrap and regtest pending on x86_64-unknown-linux-gnu, I guess
> > there will be some fallout of such change ...
>
> The following is what I need to get it to boostrap on
> x86_64-unknown-linux-gnu (with all languages enabled).
>
> I think some cases warrant a TYPE_PRECISION_RAW but most
> are fixing existing errors. For some cases I didn't dig
> deep enough if the code also needs to compare TYPE_VECTOR_SUBPARTS.
>
> The testsuite is running and shows more issues ...
>
> I put this on hold for the moment but hope to get back to it at
> some point. I'll followup with the testresults though.
Attached - it's not too much it seems, but things repeat of course.
Richard.
[-- Attachment #2: Type: application/x-xz, Size: 10948 bytes --]
next prev parent reply other threads:[~2023-06-09 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:23 Richard Biener
2023-06-09 11:53 ` Richard Biener [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-27 9:45 Richard Biener
2023-06-27 9:47 ` Jakub Jelinek
2023-06-29 4:04 ` Li, Pan2
2023-06-29 4:18 ` Li, Pan2
2023-06-29 10:03 ` juzhe.zhong
2023-06-29 10:06 ` Robin Dapp
2023-06-29 10:07 ` Robin Dapp
2023-06-29 4:25 ` Jeff Law
2023-06-29 8:11 ` Richard Biener
2023-06-29 9:55 ` Robin Dapp
2023-06-29 9:56 ` Richard Biener
2023-06-29 11:07 ` Robin Dapp
2023-06-29 15:13 ` Jeff Law
2023-06-09 7:40 Richard Biener
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=nycvar.YFH.7.77.849.2306091151570.4723@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
/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).