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/112733] [14 Regression] ICE: Segmentation fault in wide-int.cc during GIMPLE pass: sccp Date: Tue, 28 Nov 2023 14:34:33 +0000 [thread overview] Message-ID: <bug-112733-4-aUILr29RRK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112733-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112733 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- One thing is obviously we shouldn't crash on it and will debug that. But, what multiple_of_p does (or its callers) is weird: 14552 /* Check for special cases to see if top is defined as multiple 14553 of bottom: 14554 14555 top = (X & ~(bottom - 1) ; bottom is power of 2 14556 14557 or 14558 14559 Y = X % bottom 14560 top = X - Y. */ 14561 if (code == BIT_AND_EXPR 14562 && (op2 = gimple_assign_rhs2 (stmt)) != NULL_TREE 14563 && TREE_CODE (op2) == INTEGER_CST 14564 && integer_pow2p (bottom) 14565 && wi::multiple_of_p (wi::to_widest (op2), 14566 wi::to_widest (bottom), UNSIGNED)) 14567 return true; It uses UNSIGNED, but both op2 and bottom are signed: (gdb) p debug_tree (op2) <integer_cst 0x7fffea2e5e70 type <integer_type 0x7fffea14c2a0 signed char> constant 1> $17 = void (gdb) p debug_tree (bottom) <integer_cst 0x7fffea14e000 type <integer_type 0x7fffea14c2a0 signed char> constant -128> so it is in the end multiple_of_p 1, 0xffffff................fffffffffffffffffffffffff80 where the latter has 131072 bits precision. That definitely doesn't have anything to do with what the source does (and didn't even when the precision was just 576 bits before).
next prev parent reply other threads:[~2023-11-28 14:34 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 19:12 [Bug middle-end/112733] New: " patrick at rivosinc dot com 2023-11-27 19:16 ` [Bug middle-end/112733] " pinskia at gcc dot gnu.org 2023-11-27 19:16 ` pinskia at gcc dot gnu.org 2023-11-27 19:21 ` pinskia at gcc dot gnu.org 2023-11-27 19:25 ` pinskia at gcc dot gnu.org 2023-11-28 9:02 ` rguenth at gcc dot gnu.org 2023-11-28 9:35 ` jakub at gcc dot gnu.org 2023-11-28 14:34 ` jakub at gcc dot gnu.org [this message] 2023-11-28 14:48 ` jakub at gcc dot gnu.org 2023-11-28 15:56 ` jakub at gcc dot gnu.org 2023-11-28 16:01 ` jakub at gcc dot gnu.org 2023-11-28 17:37 ` jakub at gcc dot gnu.org 2023-11-28 17:43 ` jakub at gcc dot gnu.org 2023-11-29 9:29 ` jakub at gcc dot gnu.org 2023-11-29 11:27 ` cvs-commit at gcc dot gnu.org 2023-11-30 8:15 ` cvs-commit at gcc dot gnu.org 2023-11-30 8:16 ` jakub at gcc dot gnu.org 2023-12-15 14:05 ` cvs-commit at gcc dot gnu.org 2023-12-16 0:38 ` cvs-commit at gcc dot gnu.org 2023-12-17 13:55 ` cvs-commit 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-112733-4-aUILr29RRK@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).