public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105874] [13 Regression] Incorrect codegen and ICE since g:ed6fd2aed58f2cca99f15331bf68999c0e6df370
Date: Wed, 08 Jun 2022 09:20:05 +0000 [thread overview]
Message-ID: <bug-105874-4-VoOxn9QmOm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105874-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105874
--- Comment #3 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
(In reply to Roger Sayle from comment #1)
> Hi Tamar.
> I'm truly sorry for the inconvenience. Can you try reducing again now that
> the load_register_parameters issue with the "small const structs as
> immediate constants" patch has been resolved? A small failing testcase from
> Leela's FastBoard::is_eye would be extremely helpful. Thanks in advance.
No Worries, I can see indeed the ICE is resolved, I'll minimize the benchmark.
Cheers!
next prev parent reply other threads:[~2022-06-08 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 14:45 [Bug middle-end/105874] New: " tnfchris at gcc dot gnu.org
2022-06-07 17:58 ` [Bug middle-end/105874] " roger at nextmovesoftware dot com
2022-06-07 19:14 ` roger at nextmovesoftware dot com
2022-06-08 9:20 ` tnfchris at gcc dot gnu.org [this message]
2022-06-08 13:08 ` roger at nextmovesoftware dot com
2022-06-08 15:42 ` tnfchris at gcc dot gnu.org
2022-06-08 19:43 ` ebotcazou at gcc dot gnu.org
2022-06-08 19:44 ` cvs-commit at gcc dot gnu.org
2022-06-09 7:45 ` tnfchris at gcc dot gnu.org
2022-06-09 11:05 ` roger at nextmovesoftware dot com
2022-07-01 8:01 ` cvs-commit 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-105874-4-VoOxn9QmOm@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).