From: Andrew Pinski <pinskia@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR 109919: ICE in emit_move_insn with some bit tests
Date: Sat, 20 May 2023 20:28:02 -0700 [thread overview]
Message-ID: <CA+=Sn1m8FYf+s0uR3eY1pFERoEpSXhz9VGtuOoZqaiAP=kFCWA@mail.gmail.com> (raw)
In-Reply-To: <8110c2f0-cf70-3360-b59a-5f1df798cebd@gmail.com>
On Sat, May 20, 2023 at 8:25 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
>
> On 5/20/23 21:05, Andrew Pinski wrote:
> > On Sat, May 20, 2023 at 6:26 PM Jeff Law via Gcc-patches
> > <gcc-patches@gcc.gnu.org> wrote:
> >>
> >>
> >>
> >> On 5/20/23 19:09, Andrew Pinski via Gcc-patches wrote:
> >>> The problem is I used expand_expr with the target but
> >>> we don't want to use the target here as it is the wrong
> >>> mode for the original expression. The testcase would ICE
> >>> deap down while trying to do a move to use the target.
> >>> Anyways just calling expand_expr with NULL_EXPR fixes
> >>> the issue.
> >>>
> >>> Committed as obvious after a bootstrap/test on x86_64-linux-gnu.
> >>>
> >>> PR middle-end/109919
> >>>
> >>> gcc/ChangeLog:
> >>>
> >>> * expr.cc (expand_single_bit_test): Don't use the
> >>> target for expand_expr.
> >>>
> >>> gcc/testsuite/ChangeLog:
> >>>
> >>> * gcc.c-torture/compile/pr109919-1.c: New test.
> >> Thanks. I'll respin the targets that failed. If you don't hear from
> >> me, assume everything is happy again after this fix.
> >
> > Oh, I am going to test on aarch64-linux-gnu too just in case.
> > Expand is definitely something which I am not used to working on so I
> > figured I had made a mistake somewhere. I suspect I still made a
> > similar mistake later on too.
> I'm seeing some execution failures. Building H8 bits now to debug as
> it's the target I'm most familiar with. More info as it's available.
Is H8 big-endian? I could have messed that up.
Thanks,
Andrew Pinski
>
> jeff
next prev parent reply other threads:[~2023-05-21 3:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 1:09 Andrew Pinski
2023-05-21 1:25 ` Jeff Law
2023-05-21 3:05 ` Andrew Pinski
2023-05-21 3:25 ` Jeff Law
2023-05-21 3:28 ` Andrew Pinski [this message]
2023-05-21 3:32 ` Andrew Pinski
2023-05-21 3:47 ` Andrew Pinski
2023-05-21 4:34 ` Jeff Law
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='CA+=Sn1m8FYf+s0uR3eY1pFERoEpSXhz9VGtuOoZqaiAP=kFCWA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@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).