public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/103513] New: [12 Regression] ICE in evaluate_conditions_for_known_args, at ipa-fnsummary.c:516 with -O2 and above Date: Wed, 01 Dec 2021 06:24:45 +0000 [thread overview] Message-ID: <bug-103513-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103513 Bug ID: 103513 Summary: [12 Regression] ICE in evaluate_conditions_for_known_args, at ipa-fnsummary.c:516 with -O2 and above Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: haoxintu at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Hi all. It seems to be a recent regression issue. $cat small.c #include <stdint.h> uint16_t(a)(); uint16_t(b)(int f, int g) { return f * g; } uint64_t c(); void d() { c(a()); } uint64_t c(int e) { for (;;) if (b(20, -1L == e)) for (;;) ; return 0; } $gcc -c -O2 small.c during IPA pass: inline small.c:12:1: internal compiler error: in evaluate_conditions_for_known_args, at ipa-fnsummary.c:516 12 | } | ^ 0x6c881e evaluate_conditions_for_known_args ../../gcc/ipa-fnsummary.c:516 0xa6133f do_estimate_edge_size(cgraph_edge*) ../../gcc/ipa-inline-analysis.c:330 0xa6247a estimate_edge_size ../../gcc/ipa-inline.h:79 0xa6247a estimate_edge_growth ../../gcc/ipa-inline.h:100 0xa6247a do_estimate_growth_1 ../../gcc/ipa-inline-analysis.c:429 0xa625fd cgraph_node::call_for_symbol_and_aliases(bool (*)(cgraph_node*, void*), void*, bool) ../../gcc/cgraph.h:3411 0xa625fd estimate_growth(cgraph_node*) ../../gcc/ipa-inline-analysis.c:467 0x18d8d6c inline_small_functions ../../gcc/ipa-inline.c:1980 0x18d8d6c ipa_inline ../../gcc/ipa-inline.c:2743 0x18d8d6c execute ../../gcc/ipa-inline.c:3142 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/home/haoxin/haoxin-data/compilers/gcc/build/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --prefix=/home/haoxin/haoxin-data/compilers/gcc/build --enable-bootstrap --enable-checking=release --enable-languages=c,c++ --enable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20211130 (experimental) (GCC) Can also quickly check here: https://godbolt.org/z/W18G8jn7E Thanks, Haoxin
next reply other threads:[~2021-12-01 6:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-01 6:24 haoxintu at gmail dot com [this message] 2021-12-01 6:25 ` [Bug ipa/103513] " pinskia at gcc dot gnu.org 2021-12-01 6:31 ` pinskia at gcc dot gnu.org 2021-12-01 7:24 ` rguenth at gcc dot gnu.org 2021-12-01 7:36 ` pinskia at gcc dot gnu.org 2021-12-01 9:23 ` [Bug ipa/103513] [12 Regression] ICE in evaluate_conditions_for_known_args, at ipa-fnsummary.c:516 with -O2 and above since r12-5531-g1b0acc4b800b589a marxin at gcc dot gnu.org 2021-12-01 20:34 ` dcb314 at hotmail dot com 2021-12-09 20:55 ` zhendong.su at inf dot ethz.ch 2021-12-12 17:12 ` hubicka at gcc dot gnu.org 2021-12-13 8:39 ` cvs-commit at gcc dot gnu.org 2021-12-13 8:41 ` hubicka 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-103513-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).