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 middle-end/112733] [14 Regression] ICE: Segmentation fault in wide-int.cc during GIMPLE pass: sccp Date: Tue, 28 Nov 2023 09:02:26 +0000 [thread overview] Message-ID: <bug-112733-4-sj9MkQbVAe@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, stack corruption. Last good frame: #0 wi::divmod_internal (quotient=0x0, remainder_len=0x7fffffffc8fc, remainder=0x7fffffffc990, dividend_val=0x7ffff71c4e68, dividend_len=1, dividend_prec=131072, divisor_val=0x7ffff702d010, divisor_len=1, divisor_prec=131072, sgn=UNSIGNED, oflow=0x0) at /space/rguenther/src/gcc/gcc/wide-int.cc:1800 #1 0x00000000011ec195 in wi::mod_trunc<generic_wide_int<wi::extended_tree<131072> >, generic_wide_int<wi::extended_tree<131072> > > (x=..., y=..., sgn=UNSIGNED, overflow=0x0) at /space/rguenther/src/gcc/gcc/wide-int.h:3382 #2 0x00000000011e90ee in wi::multiple_of_p<generic_wide_int<wi::extended_tree<131072> >, generic_wide_int<wi::extended_tree<131072> > > (x=..., y=..., sgn=UNSIGNED) at /space/rguenther/src/gcc/gcc/wide-int.h:3549 #3 0x00000000011d564d in multiple_of_p ( type=<integer_type 0x7ffff702b2a0 signed char>, top=<ssa_name 0x7ffff7016f30 2>, bottom=<integer_cst 0x7ffff702d000>, nowrap=true) at /space/rguenther/src/gcc/gcc/fold-const.cc:14554 #4 0x00000000011caa58 in fold_binary_loc (loc=0, code=BIT_AND_EXPR, type=<integer_type 0x7ffff702b2a0 signed char>, op0=<ssa_name 0x7ffff7016f30 2>, op1=<integer_cst 0x7ffff702d000>) at /space/rguenther/src/gcc/gcc/fold-const.cc:12112 #5 0x00000000011d4356 in fold_build2_loc (loc=0, code=BIT_AND_EXPR, type=<integer_type 0x7ffff702b2a0 signed char>, op0=<ssa_name 0x7ffff7016f30 2>, op1=<integer_cst 0x7ffff702d000>) at /space/rguenther/src/gcc/gcc/fold-const.cc:14128 #6 0x0000000001848eba in analyze_and_compute_bitop_with_inv_effect ( loop=0x7ffff700e4b0, phidef=<ssa_name 0x7ffff71e5000 4>, niter=<plus_expr 0x7ffff71f2230>) at /space/rguenther/src/gcc/gcc/tree-scalar-evolution.cc:3719 and we end up with (gdb) p divisor_blocks_needed $36 = 4096 if (remainder) { *remainder_len = wi_pack (remainder, b_remainder, n, dividend_prec); (gdb) p n $50 = 4096 (gdb) p dividend_prec $51 = 128 (gdb) p remainder $52 = (long *) 0x7fffffffc990 (gdb) p b_remainder $53 = (unsigned int *) 0x7ffffffec0f0 and that wi_pack faults.
next prev parent reply other threads:[~2023-11-28 9:02 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 [this message] 2023-11-28 9:35 ` jakub at gcc dot gnu.org 2023-11-28 14:34 ` jakub at gcc dot gnu.org 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-sj9MkQbVAe@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).