public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/112380] [14 regression] ICE when building Mesa (in combine, internal compiler error: in simplify_subreg) since r14-2526-g8911879415d6c2
Date: Sun, 05 Nov 2023 19:15:11 +0000 [thread overview]
Message-ID: <bug-112380-4-g55G4jLcYt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112380-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
Roger Sayle <roger at nextmovesoftware dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |roger at nextmovesoftware dot com
Status|NEW |ASSIGNED
--- Comment #10 from Roger Sayle <roger at nextmovesoftware dot com> ---
combine.cc's expand_field_assignment needs to defend against gen_lowpart (which
is gen_lowpart_for_combine) returning a CLOBBER. Otherwise, we end up calling
simplify_set on:
(set (reg:DI 134)
(and:DI (subreg:DI (ior:SI (ior:SI (and:SI (subreg:SI (reg/v:TI 114 [
sampler ]) 0)
(const_int -129280 [0xfffffffffffe0700]))
(and:SI (clobber:TI (const_int 0 [0]))
(const_int -129025 [0xfffffffffffe07ff])))
(and:SI (reg:SI 130)
(const_int 129024 [0x1f800]))) 0)
(const_int 4294967295 [0xffffffff])))
where if you look closely the "(clobber:TI (const_int 0))" causes no end of fun
in simplify_rtx; it's not surprising that an assert is eventually triggered in
simplify_subreg.
I'm testing a patch.
next prev parent reply other threads:[~2023-11-05 19:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 14:32 [Bug rtl-optimization/112380] New: [14 regression] ICE when building mesa sjames at gcc dot gnu.org
2023-11-04 14:32 ` [Bug rtl-optimization/112380] " sjames at gcc dot gnu.org
2023-11-04 15:45 ` sjames at gcc dot gnu.org
2023-11-04 15:57 ` sjames at gcc dot gnu.org
2023-11-04 17:01 ` pinskia at gcc dot gnu.org
2023-11-04 17:47 ` [Bug rtl-optimization/112380] [14 regression] ICE when building Mesa (in combine, internal compiler error: in simplify_subreg) sjames at gcc dot gnu.org
2023-11-04 18:02 ` pinskia at gcc dot gnu.org
2023-11-04 19:16 ` [Bug rtl-optimization/112380] [14 regression] ICE when building Mesa (in combine, internal compiler error: in simplify_subreg) since r14-4612-g6decda1a35be57 sjames at gcc dot gnu.org
2023-11-04 19:32 ` pinskia at gcc dot gnu.org
2023-11-04 19:40 ` pinskia at gcc dot gnu.org
2023-11-05 9:19 ` sjames at gcc dot gnu.org
2023-11-05 19:15 ` roger at nextmovesoftware dot com [this message]
2023-11-12 22:42 ` [Bug rtl-optimization/112380] [14 regression] ICE when building Mesa (in combine, internal compiler error: in simplify_subreg) since r14-2526-g8911879415d6c2 sjames at gcc dot gnu.org
2023-11-12 23:26 ` roger at nextmovesoftware dot com
2023-12-11 17:33 ` cvs-commit at gcc dot gnu.org
2023-12-16 9:25 ` roger at nextmovesoftware dot com
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-112380-4-g55G4jLcYt@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).