public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/114159] New: [13/14 Regression] ICE: in call_info, at analyzer/call-info.cc:143 with -fanalyzer -fanalyzer-call-summaries --param=analyzer-max-svalue-depth=0 Date: Wed, 28 Feb 2024 20:44:11 +0000 [thread overview] Message-ID: <bug-114159-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114159 Bug ID: 114159 Summary: [13/14 Regression] ICE: in call_info, at analyzer/call-info.cc:143 with -fanalyzer -fanalyzer-call-summaries --param=analyzer-max-svalue-depth=0 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 57572 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57572&action=edit auto-reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -fanalyzer -fanalyzer-call-summaries --param=analyzer-max-svalue-depth=0 pr36690-2.i during IPA pass: analyzer pr36690-2.i: In function 'main': pr36690-2.i:13:3: internal compiler error: in call_info, at analyzer/call-info.cc:143 13 | foo(); | ^~~~~ 0xdc029b ana::call_info::call_info(ana::call_details const&) /repo/gcc-trunk/gcc/analyzer/call-info.cc:143 0xdc029b ana::call_info::call_info(ana::call_details const&) /repo/gcc-trunk/gcc/analyzer/call-info.cc:139 0x190bf18 ana::call_summary_edge_info::call_summary_edge_info(ana::call_details const&, function*, ana::call_summary*, ana::extrinsic_state const&) /repo/gcc-trunk/gcc/analyzer/engine.cc:1619 0x190bf18 std::enable_if<!std::is_array<ana::call_summary_edge_info>::value, std::unique_ptr<ana::call_summary_edge_info, std::default_delete<ana::call_summary_edge_info> > >::type make_unique<ana::call_summary_edge_info, ana::call_details&, function*&, ana::call_summary*&, ana::extrinsic_state const&>(ana::call_details&, function*&, ana::call_summary*&, ana::extrinsic_state const&) /repo/gcc-trunk/gcc/make-unique.h:41 0x190bf18 ana::exploded_node::replay_call_summary(ana::exploded_graph&, ana::supernode const*, gcall const*, ana::program_state*, ana::path_context*, function*, ana::call_summary*, ana::region_model_context*) /repo/gcc-trunk/gcc/analyzer/engine.cc:1734 0x190c0bd ana::exploded_node::replay_call_summaries(ana::exploded_graph&, ana::supernode const*, gcall const*, ana::program_state*, ana::path_context*, function*, ana::per_function_data*, ana::region_model_context*) /repo/gcc-trunk/gcc/analyzer/engine.cc:1677 0x19119df ana::exploded_node::on_stmt(ana::exploded_graph&, ana::supernode const*, gimple const*, ana::program_state*, ana::uncertainty_t*, bool*, ana::path_context*) /repo/gcc-trunk/gcc/analyzer/engine.cc:1499 0x19143ba ana::exploded_graph::process_node(ana::exploded_node*) /repo/gcc-trunk/gcc/analyzer/engine.cc:4124 0x191532a ana::exploded_graph::process_worklist() /repo/gcc-trunk/gcc/analyzer/engine.cc:3515 0x1917a85 ana::impl_run_checkers(ana::logger*) /repo/gcc-trunk/gcc/analyzer/engine.cc:6209 0x1918996 ana::run_checkers() /repo/gcc-trunk/gcc/analyzer/engine.cc:6300 0x19075f8 execute /repo/gcc-trunk/gcc/analyzer/analyzer-pass.cc:87 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-9216-20240228150317-g5c01ede02a1-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --disable-bootstrap --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r14-9216-20240228150317-g5c01ede02a1-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.1 20240228 (experimental) (GCC)
next reply other threads:[~2024-02-28 20:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 20:44 zsojka at seznam dot cz [this message] 2024-02-29 8:15 ` [Bug analyzer/114159] " rguenth at gcc dot gnu.org 2024-02-29 16:24 ` dmalcolm at gcc dot gnu.org 2024-02-29 23:16 ` cvs-commit at gcc dot gnu.org 2024-02-29 23:21 ` [Bug analyzer/114159] [13 " dmalcolm at gcc dot gnu.org 2024-05-13 11:28 ` rguenth at gcc dot gnu.org 2024-05-21 9:19 ` 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-114159-4@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).