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 tree-optimization/110603] [14 Regression] GCC, ICE: internal compiler error: in verify_range, at value-range.cc:1104 Date: Mon, 10 Jul 2023 06:36:01 +0000 [thread overview] Message-ID: <bug-110603-4-2Gyr4ySbkT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110603-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110603 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2023-07-10 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. (gdb) p lb $1 = {<wide_int_storage> = {val = {2, 45595810, 140737488342608, 140737488342672, 140737488341240, 2147483664, 8, 140737339338752, 0}, len = 1, precision = 32}, static is_sign_extended = true} (gdb) p ub $2 = {<wide_int_storage> = {val = {1, 1, 1, 1, 140737488341320, 2147483664, 140737471578113, 0, 140735340871686}, len = 1, precision = 32}, static is_sign_extended = true} from #4 0x0000000002b7c5d7 in (anonymous namespace)::try_substitute_return_value ( gsi=0x7fffffffda18, info=..., res=...) at /space/rguenther/src/gcc/gcc/gimple-ssa-sprintf.cc:4254 else if (lhs && types_compatible_p (TREE_TYPE (lhs), integer_type_node)) { bool setrange = false; if (safe && (info.bounded || retval[1] < info.objsize) && (retval[0] < target_int_max () && retval[1] < target_int_max ())) { /* If the result is in a valid range bounded by the size of the destination set it so that it can be used for subsequent optimizations. */ int prec = TYPE_PRECISION (integer_type_node); wide_int min = wi::shwi (retval[0], prec); wide_int max = wi::shwi (retval[1], prec); value_range r (TREE_TYPE (lhs), min, max); set_range_info (lhs, r); The issue is likely older but only triggered with recent ranger changes (on the verifier side?).
next prev parent reply other threads:[~2023-07-10 6:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-09 11:34 [Bug c/110603] New: " 141242068 at smail dot nju.edu.cn 2023-07-09 14:57 ` [Bug tree-optimization/110603] [14 Regression] " pinskia at gcc dot gnu.org 2023-07-10 6:36 ` rguenth at gcc dot gnu.org [this message] 2023-10-17 12:10 ` rguenth at gcc dot gnu.org 2024-01-02 20:39 ` doko at gcc dot gnu.org 2024-01-09 18:06 ` [Bug tree-optimization/110603] [14 Regression] GCC, ICE: internal compiler error: in verify_range, at value-range.cc:1104 since r14-255 jakub at gcc dot gnu.org 2024-01-10 10:31 ` aldyh at gcc dot gnu.org 2024-01-23 11:16 ` jakub at gcc dot gnu.org 2024-01-27 12:48 ` jakub at gcc dot gnu.org 2024-01-29 9:21 ` cvs-commit at gcc dot gnu.org 2024-01-29 9:30 ` 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-110603-4-2Gyr4ySbkT@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).