From: Jakub Jelinek <jakub@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 18/12] Handle BITINT_TYPE in build_{, minus_}one_cst [PR102989]
Date: Tue, 5 Sep 2023 23:52:19 +0200 [thread overview]
Message-ID: <ZPejE32RgDKZTFvd@tucnak> (raw)
In-Reply-To: <CA+=Sn1mO2NW4pqRXtD4qcr+hdfJ_fB4C1ES-57dD47vWxbqLXg@mail.gmail.com>
On Tue, Sep 05, 2023 at 02:42:39PM -0700, Andrew Pinski wrote:
> On Tue, Sep 5, 2023 at 12:31 AM Jakub Jelinek via Gcc-patches
> > Recent match.pd changes trigger ICE in build_minus_one_cst, apparently
> > I forgot to handle BITINT_TYPE in these (while I've handled it in
> > build_zero_cst).
> >
> > Will commit as obvious together with the rest of the series when the last
> > patches are approved.
>
> I assume there was a testcase that will be added when _BitInt
> front-end support gets added.
After working around the build_nonstandard_integer_type in match.pd (in that
case the single one, I know there are some others) the ICE was on
dg-torture/bitint-42.c at -O1/-Os, so no new testcase needs to be added.
Jakub
prev parent reply other threads:[~2023-09-05 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 7:30 [PATCH 18/12] Handle BITINT_TYPE in build_{,minus_}one_cst [PR102989] Jakub Jelinek
2023-09-05 21:42 ` [PATCH 18/12] Handle BITINT_TYPE in build_{, minus_}one_cst [PR102989] Andrew Pinski
2023-09-05 21:52 ` Jakub Jelinek [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=ZPejE32RgDKZTFvd@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=rguenther@suse.de \
/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).