public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/112560] [14 Regression] ICE in try_combine on pr112494.c Date: Mon, 08 Apr 2024 20:22:50 +0000 [thread overview] Message-ID: <bug-112560-4-sr4zL6wD9P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112560-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112560 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:eaccdba315b86d374a4e72b9dd8fefb0fc3cc5ee commit r14-9847-geaccdba315b86d374a4e72b9dd8fefb0fc3cc5ee Author: Uros Bizjak <ubizjak@gmail.com> Date: Mon Apr 8 20:54:30 2024 +0200 combine: Fix ICE in try_combine on pr112494.c [PR112560] The compiler, configured with --enable-checking=yes,rtl,extra ICEs with: internal compiler error: RTL check: expected elt 0 type 'e' or 'u', have 'E' (rtx unspec) in try_combine, at combine.cc:3237 This is 3236 /* Just replace the CC reg with a new mode. */ 3237 SUBST (XEXP (*cc_use_loc, 0), newpat_dest); 3238 undobuf.other_insn = cc_use_insn; in combine.cc, where *cc_use_loc is (unspec:DI [ (reg:CC 17 flags) ] UNSPEC_PUSHFL) combine assumes CC must be used inside of a comparison and uses XEXP (..., 0) without checking on the RTX type of the argument. Replace cc_use_loc with the entire new RTX only in case cc_use_loc satisfies COMPARISON_P predicate. Otherwise scan the entire cc_use_loc RTX for CC reg to be updated with a new mode. PR rtl-optimization/112560 gcc/ChangeLog: * combine.cc (try_combine): Replace cc_use_loc with the entire new RTX only in case cc_use_loc satisfies COMPARISON_P predicate. Otherwise scan the entire cc_use_loc RTX for CC reg to be updated with a new mode. * config/i386/i386.md (@pushf<mode>2): Allow all CC modes for operand 1.
next prev parent reply other threads:[~2024-04-08 20:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-16 7:23 [Bug middle-end/112560] New: " jakub at gcc dot gnu.org 2023-11-16 7:24 ` [Bug middle-end/112560] [14 Regression] " jakub at gcc dot gnu.org 2023-11-18 6:17 ` pinskia at gcc dot gnu.org 2023-11-18 6:17 ` pinskia at gcc dot gnu.org 2023-11-28 16:00 ` ubizjak at gmail dot com 2023-11-28 17:33 ` ubizjak at gmail dot com 2023-11-29 9:37 ` ubizjak at gmail dot com 2024-03-11 11:54 ` [Bug rtl-optimization/112560] " ubizjak at gmail dot com 2024-03-12 17:54 ` ubizjak at gmail dot com 2024-04-08 20:22 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-09 8:26 ` rguenth at gcc dot gnu.org 2024-04-09 8:28 ` ubizjak at gmail dot com 2024-04-10 17:55 ` segher at gcc dot gnu.org 2024-04-10 18:34 ` ubizjak at gmail dot com 2024-04-10 22:44 ` segher at gcc dot gnu.org 2024-04-11 6:33 ` ubizjak at gmail 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-112560-4-sr4zL6wD9P@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: linkBe 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).