public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113988] during GIMPLE pass: bitintlower: internal compiler error: in lower_stmt, at gimple-lower-bitint.cc:5470
Date: Thu, 22 Feb 2024 08:52:14 +0000 [thread overview]
Message-ID: <bug-113988-4-YgVsJ6t4Pc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113988-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113988
--- Comment #23 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 22 Feb 2024, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113988
>
> --- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Yeah, I was worried about partial ints. Or it could be punt if TYPE_MODEs are
> different and at least one of them is BLKmode.
Well, then you can also check whether one mode is BLKmode.
Btw, I think forwprop is lucky if it really changes
_2 = VIEW_CONVERT_EXPR<uint256_t>(x);
to
_2 = (uint256_t) x_1(D);
because match on its own would create
_2 = (uint256_t) x;
which would be invalid GIMPLE. So are you sure it's not
update-address-taken first rewriting x to a register?
For 'foo' I see x becomes a register already during into-SSA so
another fix might be to re-consider and make x a non-register
because of that V_C_E? (and hopefully the match pattern would
then not be applied, but I'm not 100% sure on that)
In principle there's nothing wrong about the transform it's
the use of uint256_t that makes this problematic.
So maybe we should bite the bullet and try the memcpy folding
fix even at this stage ...
next prev parent reply other threads:[~2024-02-22 8:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:51 [Bug c++/113988] New: " janschultke at googlemail dot com
2024-02-19 10:00 ` [Bug middle-end/113988] " pinskia at gcc dot gnu.org
2024-02-19 10:01 ` janschultke at googlemail dot com
2024-02-19 10:05 ` jakub at gcc dot gnu.org
2024-02-19 14:22 ` rguenth at gcc dot gnu.org
2024-02-19 14:30 ` rguenth at gcc dot gnu.org
2024-02-19 14:34 ` rguenth at gcc dot gnu.org
2024-02-19 14:34 ` jakub at gcc dot gnu.org
2024-02-19 14:37 ` rguenth at gcc dot gnu.org
2024-02-19 14:39 ` rguenth at gcc dot gnu.org
2024-02-19 14:40 ` jakub at gcc dot gnu.org
2024-02-19 14:42 ` jakub at gcc dot gnu.org
2024-02-19 14:44 ` rguenther at suse dot de
2024-02-19 15:35 ` hjl.tools at gmail dot com
2024-02-19 18:57 ` jakub at gcc dot gnu.org
2024-02-20 7:32 ` rguenth at gcc dot gnu.org
2024-02-20 9:12 ` rsandifo at gcc dot gnu.org
2024-02-21 12:40 ` jakub at gcc dot gnu.org
2024-02-21 12:50 ` jakub at gcc dot gnu.org
2024-02-22 7:47 ` rguenther at suse dot de
2024-02-22 8:10 ` jakub at gcc dot gnu.org
2024-02-22 8:34 ` rguenther at suse dot de
2024-02-22 8:37 ` jakub at gcc dot gnu.org
2024-02-22 8:52 ` rguenther at suse dot de [this message]
2024-02-23 10:06 ` jakub at gcc dot gnu.org
2024-02-24 11:46 ` jakub at gcc dot gnu.org
2024-02-25 18:37 ` zsojka at seznam dot cz
2024-02-26 21:41 ` zsojka at seznam dot cz
2024-02-27 11:53 ` jakub at gcc dot gnu.org
2024-02-28 8:55 ` cvs-commit at gcc dot gnu.org
2024-02-28 9:01 ` jakub at gcc dot gnu.org
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=bug-113988-4-YgVsJ6t4Pc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).