public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iamanonymous.cs at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/114778] New: ICE: internal compiler error: in get_region_for_local, at analyzer/region.cc:1366 Date: Fri, 19 Apr 2024 01:55:29 +0000 [thread overview] Message-ID: <bug-114778-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114778 Bug ID: 114778 Summary: ICE: internal compiler error: in get_region_for_local, at analyzer/region.cc:1366 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: iamanonymous.cs at gmail dot com Target Milestone: --- Compiler Explorer: https://godbolt.org/z/r3E89h944 ******************************************************************************* OS and Platform: $ uname -a: Linux ubuntu 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ******************************************************************************* gcc version: $ gcc -v Using built-in specs. COLLECT_GCC=/root/gcc_set/202404101100/bin/gcc COLLECT_LTO_WRAPPER=/root/gcc_set/202404101100/libexec/gcc/x86_64-pc-linux-gnu/14.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc/configure --prefix=/root/gcc_set/202404101100 --with-gmp=/root/build_essential --with-mpfr=/root/build_essential --with-mpc=/root/build_essential --enable-languages=c,c++ --disable-multilib --with-sanitizer=address,undefined,thread,leak Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.1 20240410 (experimental) (GCC) git version: 0774240b4df9a9bc48ce33a9625788e402498f5a ******************************************************************************* Program: $ cat mutant.c int b; int a(char *c) { return c[9]; } void d() { struct e { char g[b] } f(struct e arg) { a(arg.g); } if (f != 'd') ; } ******************************************************************************* Command Lines: $ gcc -fanalyzer -c mutant.c mutant.c: In function ‘d’: mutant.c:6:3: warning: no semicolon at end of struct or union 6 | } f(struct e arg) { | ^ mutant.c:9:9: warning: comparison between pointer and integer 9 | if (f != 'd') | ^~ during IPA pass: analyzer mutant.c: In function ‘a’: mutant.c:2:26: internal compiler error: in get_region_for_local, at analyzer/region.cc:1366 2 | int a(char *c) { return c[9]; } | ~^~~ 0x88c303 ana::frame_region::get_region_for_local(ana::region_model_manager*, tree_node*, ana::region_model_context const*) const ../../gcc/gcc/analyzer/region.cc:1366 0x14815a2 ana::region_model::get_lvalue(ana::path_var, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:2466 0x148541a ana::region_model::get_rvalue_1(ana::path_var, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:2532 0x1481ccc ana::region_model::get_rvalue(ana::path_var, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:2610 0x2173639 ana::region_model::check_region_bounds(ana::region const*, ana::access_direction, ana::svalue const*, ana::region_model_context*) const ../../gcc/gcc/analyzer/bounds-checking.cc:1396 0x147f3c9 ana::region_model::check_region_access(ana::region const*, ana::access_direction, ana::svalue const*, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:3095 0x147f3c9 ana::region_model::check_region_access(ana::region const*, ana::access_direction, ana::svalue const*, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:3084 0x147f3c9 ana::region_model::check_region_for_read(ana::region const*, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:3129 0x147f3c9 ana::region_model::check_region_for_read(ana::region const*, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:3126 0x147f3c9 ana::region_model::get_store_value(ana::region const*, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:2690 0x1481ccc ana::region_model::get_rvalue(ana::path_var, ana::region_model_context*) const ../../gcc/gcc/analyzer/region-model.cc:2610 0x148664c ana::region_model::on_assignment(gassign const*, ana::region_model_context*) ../../gcc/gcc/analyzer/region-model.cc:1244 0x144daf0 ana::exploded_node::on_stmt(ana::exploded_graph&, ana::supernode const*, gimple const*, ana::program_state*, ana::uncertainty_t*, bool*, ana::path_context*) ../../gcc/gcc/analyzer/engine.cc:1515 0x1450915 ana::exploded_graph::process_node(ana::exploded_node*) ../../gcc/gcc/analyzer/engine.cc:4125 0x145166a ana::exploded_graph::process_worklist() ../../gcc/gcc/analyzer/engine.cc:3516 0x1453c4b ana::impl_run_checkers(ana::logger*) ../../gcc/gcc/analyzer/engine.cc:6210 0x1454bb6 ana::run_checkers() ../../gcc/gcc/analyzer/engine.cc:6308 0x1443a98 execute ../../gcc/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.
next reply other threads:[~2024-04-19 1:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-19 1:55 iamanonymous.cs at gmail dot com [this message] 2024-04-22 16:49 ` [Bug analyzer/114778] ICE: " dmalcolm at gcc dot gnu.org 2024-04-22 16:50 ` dmalcolm at gcc dot gnu.org 2024-04-23 2:10 ` iamanonymous.cs at gmail dot com
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-114778-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).