From: Stafford Horne <shorne@gmail.com>
To: Simon Marchi <simark@simark.ca>
Cc: GDB patches <gdb-patches@sourceware.org>,
Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: Re: [PATCH] or1k: Fix ICE in libgcc caused by recent validate_subreg changes
Date: Mon, 9 Jun 2025 20:01:38 +0100 [thread overview]
Message-ID: <aEcvktufxzjdr95I@antec> (raw)
In-Reply-To: <ed2035f9-d5ea-4090-9d43-d6be9d40f901@simark.ca>
On Mon, Jun 09, 2025 at 02:57:46PM -0400, Simon Marchi wrote:
> On 6/9/25 2:52 PM, Stafford Horne wrote:
> > After commit eb2ea476db2 ("emit-rtl: Allow extra checks for
> > paradoxical subregs [PR119966]") paradoxical subregs or the OpenRISC
> > condition flag register (reg:BI sr_f) are no longer allowed.
> >
> > This causes and ICE in the ce1 pass which tries to get the or1k flag
> > register into an SI register, which is no longer possible.
> >
> > Adjust or1k_can_change_mode_class to allow changing the or1k flag reg to
> > SI mode which in turn allows paradoxical subregs to bre generated again.
> >
> > gcc/ChangeLog:
> >
> > PR or1k/120587
> > * config/or1k/or1k.cc (or1k_can_change_mode_class): Allow
> > changing flags mode from BI to SI to allow for paradoxical
> > subregs.
>
> Wrong mailing list I think (gcc, not gdb).
Yes sorry, I have tab completion and gdb-patches looked like gcc-patches to me.
I have resent to the correct list.
-Stafford
next prev parent reply other threads:[~2025-06-09 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 18:52 [PATCH] or1k: Fix ICE in libgcc caused by recent validate_subreg changes Stafford Horne
2025-06-09 18:57 ` Simon Marchi
2025-06-09 19:01 ` Stafford Horne [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-09 18:59 Stafford Horne
2025-06-12 16:28 ` Stafford Horne
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=aEcvktufxzjdr95I@antec \
--to=shorne@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=simark@simark.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.