public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112265] [14 Regression] GCN offloading 'libgomp.c-c++-common/for-5.c': 'internal compiler error: maximum number of generated reload insns per insn achieved (90)'
Date: Sat, 28 Oct 2023 19:44:10 +0000 [thread overview]
Message-ID: <bug-112265-4-MEP0dNeRYt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112265-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112265
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #1)
> The ICE goes away if I revert PR111000 commit
> r14-4786-gd118738e71cf4615f170fff8dabe66442206d008 "tree-optimization/111000
> - restrict invariant motion of shifts". What that now tells us I have no
> clue.
That it was a latent bug; I wonder if there is a way to expose it before that
patch. Maybe a GIMPLE testcase ...
next prev parent reply other threads:[~2023-10-28 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 16:19 [Bug target/112265] New: " tschwinge at gcc dot gnu.org
2023-10-28 19:38 ` [Bug target/112265] " tschwinge at gcc dot gnu.org
2023-10-28 19:44 ` pinskia at gcc dot gnu.org [this message]
2023-10-30 13:17 ` rguenth at gcc dot gnu.org
2023-12-20 7:59 ` tschwinge 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-112265-4-MEP0dNeRYt@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).