From: Joseph Myers <joseph@codesourcery.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Vladimir Makarov <vmakarov@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [pushed][PR112918][LRA]: Fixing IRA ICE on m68k
Date: Wed, 20 Dec 2023 20:35:41 +0000 [thread overview]
Message-ID: <6e332d9-9b54-6669-cec2-ac195b71dad@codesourcery.com> (raw)
In-Reply-To: <7e297127-85dd-4da1-947d-f4935cb25bc9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Mon, 18 Dec 2023, Jeff Law wrote:
>
>
> On 12/18/23 15:16, Vladimir Makarov wrote:
> > The following patch fixes
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918
> >
> > The patch was successfully bootstrapped and tested on x86-64, aarch64, and
> > ppc64.
> >
> > The patch affects a sensitive part of LRA. So I will monitor that the
> > commit does not create serious failures on other targets. If it happens, I
> > probably revert the patch.
> I've also spun up my tester with this patch. We should know if there's any
> fallout on the cross targets by tomorrow AM. The native emulated targets will
> take longer to trickle in.
My glibc bot shows ICEs for arc and mips (different ICEs, so I filed two
separate bugs).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113097
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113098
https://sourceware.org/pipermail/libc-testresults/2023q4/012248.html
(The reason the bot only shows the mips ICE in nan2008 configurations is
probably that those use --with-arch-32=mips32r2 and the other
configurations don't, rather than any actual connection to the nan2008
feature itself.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-12-20 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 22:16 Vladimir Makarov
2023-12-19 0:05 ` Jeff Law
2023-12-19 3:34 ` Jeff Law
2023-12-20 20:35 ` Joseph Myers [this message]
2024-01-11 14:35 Vladimir Makarov
2024-01-12 14:33 ` YunQiang Su
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=6e332d9-9b54-6669-cec2-ac195b71dad@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=vmakarov@redhat.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).