public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [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
Date: Thu, 09 Dec 2021 20:55:57 +0000	[thread overview]
Message-ID: <bug-103513-4-tCPBEUu6fT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103513-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103513

Zhendong Su <zhendong.su at inf dot ethz.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zhendong.su at inf dot ethz.ch

--- Comment #6 from Zhendong Su <zhendong.su at inf dot ethz.ch> ---
Another test that fails at -Os and above:

[576] % gcctk -O1 -c small.c
[577] % 
[577] % gcctk -Os -c small.c
during IPA pass: inline
small.c:8:1: internal compiler error: in evaluate_conditions_for_known_args, at
ipa-fnsummary.c:516
    8 | }
      | ^
0xbd4256 evaluate_conditions_for_known_args
        ../../gcc-trunk/gcc/ipa-fnsummary.c:516
0xbd952e evaluate_properties_for_edge(cgraph_edge*, bool, unsigned int*,
unsigned int*, ipa_auto_call_arg_values*, bool)
        ../../gcc-trunk/gcc/ipa-fnsummary.c:726
0xbf0323 do_estimate_edge_time(cgraph_edge*, sreal*)
        ../../gcc-trunk/gcc/ipa-inline-analysis.c:197
0xbf1d34 do_estimate_edge_size(cgraph_edge*)
        ../../gcc-trunk/gcc/ipa-inline-analysis.c:319
0x1c0bc14 estimate_edge_size
        ../../gcc-trunk/gcc/ipa-inline.h:79
0x1c0bc14 estimate_edge_growth
        ../../gcc-trunk/gcc/ipa-inline.h:100
0x1c0eb89 want_inline_small_function_p
        ../../gcc-trunk/gcc/ipa-inline.c:912
0x1c1425c inline_small_functions
        ../../gcc-trunk/gcc/ipa-inline.c:2050
0x1c1425c ipa_inline
        ../../gcc-trunk/gcc/ipa-inline.c:2756
0x1c1425c execute
        ../../gcc-trunk/gcc/ipa-inline.c:3155
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.
[578] % 
[578] % cat small.c
int a;
void b(int c) {
  int d = 3;
  d ^= c < 2;
  if (d < 3 && a)
    while (1)
      b(!a);
}

  parent reply	other threads:[~2021-12-09 20:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  6:24 [Bug ipa/103513] New: [12 Regression] ICE in evaluate_conditions_for_known_args, at ipa-fnsummary.c:516 with -O2 and above haoxintu at gmail dot com
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 [this message]
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-tCPBEUu6fT@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: link
Be 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).