public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/105333] [10/11/12 Regression] ICE: in simplify_subreg, at simplify-rtx.cc:7346 with -Og -fno-tree-coalesce-vars -fno-tree-fre Date: Thu, 21 Apr 2022 11:19:28 +0000 [thread overview] Message-ID: <bug-105333-4-i5QpijYnol@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105333-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105333 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-04-21 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |segher at gcc dot gnu.org Target Milestone|--- |10.4 Priority|P3 |P2 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. #1 0x000000000142c6af in simplify_context::simplify_subreg ( this=0x7fffffffb3b8, outermode=E_SImode, op=0x7ffff668b5d0, innermode=E_VOIDmode, byte=...) (gdb) p debug_rtx( op) (const_wide_int 0x0fffffffffffffffe) (gdb) bt #0 fancy_abort ( file=0x2e7a200 "/home/rguenther/src/gcc3/gcc/simplify-rtx.cc", line=7346, function=0x2e7e100 <simplify_context::simplify_subreg(machine_mode, rtx_def*, machine_mode, poly_int<1u, unsigned long>)::__FUNCTION__> "simplify_subreg") at /home/rguenther/src/gcc3/gcc/diagnostic.cc:2024 #1 0x000000000142c6af in simplify_context::simplify_subreg ( this=0x7fffffffb3b8, outermode=E_SImode, op=0x7ffff668b5d0, innermode=E_VOIDmode, byte=...) at /home/rguenther/src/gcc3/gcc/simplify-rtx.cc:7346 #2 0x000000000142cf56 in simplify_context::simplify_subreg ( this=0x7fffffffb3b8, outermode=E_SImode, op=0x7ffff668b660, innermode=E_DImode, byte=...) at /home/rguenther/src/gcc3/gcc/simplify-rtx.cc:7444 #3 0x000000000142dfd9 in simplify_context::simplify_gen_subreg ( this=0x7fffffffb3b8, outermode=E_SImode, op=0x7ffff668b660, innermode=E_DImode, byte=...) at /home/rguenther/src/gcc3/gcc/simplify-rtx.cc:7624 ... #7 0x00000000028becb7 in gen_lowpart_for_combine (omode=E_SImode, x=0x7ffff668b660) at /home/rguenther/src/gcc3/gcc/combine.cc:11684 11684 result = gen_lowpart_common (omode, x); #8 0x0000000001410622 in simplify_context::simplify_unary_operation_1 ( this=0x7fffffffc988, code=TRUNCATE, mode=E_SImode, op=0x7ffff668b660) at /home/rguenther/src/gcc3/gcc/simplify-rtx.cc:1243 which does if (GET_MODE (op) != VOIDmode) { temp = simplify_truncation (mode, op, GET_MODE (op)); if (temp) return temp; } /* If we know that the value is already truncated, we can replace the TRUNCATE with a SUBREG. */ if (known_eq (GET_MODE_NUNITS (mode), 1) && (TRULY_NOOP_TRUNCATION_MODES_P (mode, GET_MODE (op)) || truncated_to_mode (mode, op))) { temp = rtl_hooks.gen_lowpart_no_emit (mode, op); so we know 'op' is VOIDmode here but gen_lowpart_for_combine isn't prepared for this?
next prev parent reply other threads:[~2022-04-21 11:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-21 10:47 [Bug rtl-optimization/105333] New: " zsojka at seznam dot cz 2022-04-21 11:19 ` rguenth at gcc dot gnu.org [this message] 2022-04-21 12:38 ` [Bug rtl-optimization/105333] [10/11/12 Regression] ICE: in simplify_subreg, at simplify-rtx.cc:7346 with -Og -fno-tree-coalesce-vars -fno-tree-fre since r10-1094-g9919f5fe87a3def1 marxin at gcc dot gnu.org 2022-04-21 13:55 ` jakub at gcc dot gnu.org 2022-04-22 11:38 ` cvs-commit at gcc dot gnu.org 2022-04-22 11:39 ` [Bug rtl-optimization/105333] [10/11 " jakub at gcc dot gnu.org 2022-05-06 23:44 ` cvs-commit at gcc dot gnu.org 2022-05-09 11:26 ` [Bug rtl-optimization/105333] [10 " jakub at gcc dot gnu.org 2022-05-10 8:26 ` cvs-commit at gcc dot gnu.org 2022-05-10 10:29 ` jakub 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-105333-4-i5QpijYnol@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).