public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko 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: Tue, 02 Jan 2024 20:39:15 +0000 [thread overview] Message-ID: <bug-110603-4-APPK9yP7Xo@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 Matthias Klose <doko at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |doko at gcc dot gnu.org --- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> --- also seen with 20240101 trunk, building the python-confluent-kafka package: $ cat confluent_kafka.i long _init_cimpl_dof; char _init_cimpl_dash[1], _init_cimpl_eq[1]; char PyInit_cimpl_tmpdoc[512]; int snprintf(char *, unsigned long, char *, ...); void *memset(); void PyInit_cimpl() { memset(_init_cimpl_eq, '=', sizeof(_init_cimpl_eq)); long _len = snprintf(PyInit_cimpl_tmpdoc, sizeof(PyInit_cimpl_tmpdoc), "+-%.*s-+-%.*s-+\n" "| %-*.*s | %-*.*s |\n" "+=%.*s=+=%.*s=+\n", 0, _init_cimpl_dash, 0, _init_cimpl_dash, 0, 0, "", 0, 0, "", 50, _init_cimpl_eq, 0, _init_cimpl_eq); _init_cimpl_dof += _len; } $ gcc -c -O2 -fno-strict-overflow -fstack-protector-strong -fcf-protection=full -fwrapv confluent_kafka.i during GIMPLE pass: strlen confluent_kafka.i: In function 'PyInit_cimpl': confluent_kafka.i:6:6: internal compiler error: in verify_range, at value-range.cc:1132 6 | void PyInit_cimpl() { | ^~~~~~~~~~~~ 0x6eec19 irange::verify_range() ../../src/gcc/value-range.cc:1132 0x1b52550 irange::set(tree_node*, generic_wide_int<wide_int_storage> const&, generic_wide_int<wide_int_storage> const&, value_range_kind) ../../src/gcc/value-range.cc:1076 0x1eb42ad try_substitute_return_value ../../src/gcc/gimple-ssa-sprintf.cc:4261 0x1eb42ad handle_printf_call(gimple_stmt_iterator*, pointer_query&) ../../src/gcc/gimple-ssa-sprintf.cc:4764 0x1eb2193 strlen_pass::check_and_optimize_call(bool*) ../../src/gcc/tree-ssa-strlen.cc:5452 0x1cfe639 strlen_pass::check_and_optimize_stmt(bool*) ../../src/gcc/tree-ssa-strlen.cc:5656 0x1cfe094 strlen_pass::before_dom_children(basic_block_def*) ../../src/gcc/tree-ssa-strlen.cc:5840 0x1c7fd13 dom_walker::walk(basic_block_def*) ../../src/gcc/domwalk.cc:311 0x950ef1 printf_strlen_execute ../../src/gcc/tree-ssa-strlen.cc:5899 Please submit a full bug report, with preprocessed source (by using -freport-bug).
next prev parent reply other threads:[~2024-01-02 20:39 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 2023-10-17 12:10 ` rguenth at gcc dot gnu.org 2024-01-02 20:39 ` doko at gcc dot gnu.org [this message] 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-APPK9yP7Xo@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).