public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 since r9-6999 Date: Wed, 09 Feb 2022 11:13:40 +0000 [thread overview] Message-ID: <bug-104446-4-FsKqMKADt8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104446-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104446 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The problem is that combine substutites: (insn 10 9 11 2 (set (reg/v:SI 7 sp [ a ]) (const_int 0 [0])) "pr104446.c":9:5 81 {*movsi_internal} (nil)) (insn 13 11 14 2 (set (mem/f:SI (pre_dec:SI (reg/f:SI 7 sp)) [0 S4 A32]) (reg:SI 85)) "pr104446.c":10:3 56 {*pushsi2} (expr_list:REG_DEAD (reg:SI 85) (expr_list:REG_ARGS_SIZE (const_int 16 [0x10]) (nil)))) into: (mem/f:SI (pre_dec:SI (const_int 0 [0])) [0 S4 A32]) and before it is attempted to be recognized, we do: 3347 for_each_inc_dec (newpat, count_auto_inc, &new_n_auto_inc); and that ICEs because: 3709 poly_int64 size = GET_MODE_SIZE (GET_MODE (mem)); 3710 rtx r1 = XEXP (x, 0); 3711 rtx c = gen_int_mode (-size, GET_MODE (r1)); 3712 return fn (mem, x, r1, r1, c, data); gen_int_mode (-4, VOIDmode) is invalid.
next prev parent reply other threads:[~2022-02-09 11:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-08 19:40 [Bug c/104446] New: [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 gscfq@t-online.de 2022-02-08 21:37 ` [Bug middle-end/104446] " pinskia at gcc dot gnu.org 2022-02-09 7:32 ` rguenth at gcc dot gnu.org 2022-02-09 9:04 ` [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 since r9-6999 jakub at gcc dot gnu.org 2022-02-09 11:13 ` jakub at gcc dot gnu.org [this message] 2022-02-09 11:32 ` jakub at gcc dot gnu.org 2022-02-10 7:47 ` segher at gcc dot gnu.org 2022-02-11 12:52 ` cvs-commit at gcc dot gnu.org 2022-02-11 12:53 ` [Bug middle-end/104446] [9/10/11 " jakub at gcc dot gnu.org 2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:08 ` [Bug middle-end/104446] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:23 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` 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-104446-4-FsKqMKADt8@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).