public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/109711] [14 regression] ICE (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in verify_range, at value-range.cc:1060) when building ffmpeg-4.4.4
Date: Wed, 03 May 2023 11:58:03 +0000	[thread overview]
Message-ID: <bug-109711-4-lfcBRNBNtS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109711-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
           Keywords|needs-reduction             |
   Last reconfirmed|                            |2023-05-03
     Ever confirmed|0                           |1

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
I reduced that to:

$ cat pr109711.i
void lspf2lpc();

int interpolate_lpc_q_0;

void
interpolate_lpc(int subframe_num) {
  float weight;
  if (interpolate_lpc_q_0)
    weight = subframe_num;
  else
    weight = 1.0;
  if (weight != 1.0)
    lspf2lpc();
}

void
qcelp_decode_frame() {
  int i;
  for (;; i++)
    interpolate_lpc(i);
}

$ /dev/shm/objdir2/gcc/xgcc -B/dev/shm/objdir2/gcc pr109711.i -c -O2
during IPA pass: inline
pr109711.i:21:1: internal compiler error: tree check: expected class ‘type’,
have ‘exceptional’ (error_mark) in verify_range, at value-range.cc:1060
   21 | }
      | ^
0x84dfd7 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
        /home/marxin/Programming/gcc/gcc/tree.cc:8949
0x85baff tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
        /home/marxin/Programming/gcc/gcc/tree.h:3663
0x85baff irange::verify_range()
        /home/marxin/Programming/gcc/gcc/value-range.cc:1060
0x1279d97 irange::operator=(irange const&)
        /home/marxin/Programming/gcc/gcc/value-range.cc:923
0xcd61a7 int_range<2u>::operator=(int_range<2u> const&)
        /home/marxin/Programming/gcc/gcc/value-range.h:817
0xcd61a7 evaluate_conditions_for_known_args
        /home/marxin/Programming/gcc/gcc/ipa-fnsummary.cc:517
0xcee9c5 do_estimate_edge_size(cgraph_edge*)
        /home/marxin/Programming/gcc/gcc/ipa-inline-analysis.cc:335
0xcf1465 estimate_edge_size(cgraph_edge*)
        /home/marxin/Programming/gcc/gcc/ipa-inline.h:79
0xcf1465 estimate_edge_growth(cgraph_edge*)
        /home/marxin/Programming/gcc/gcc/ipa-inline.h:100
0xcefe15 do_estimate_growth_1
        /home/marxin/Programming/gcc/gcc/ipa-inline-analysis.cc:434
0xcefef6 cgraph_node::call_for_symbol_and_aliases(bool (*)(cgraph_node*,
void*), void*, bool)
        /home/marxin/Programming/gcc/gcc/cgraph.h:3412
0xcefef6 estimate_growth(cgraph_node*)
        /home/marxin/Programming/gcc/gcc/ipa-inline-analysis.cc:472
0x1d972c4 inline_small_functions
        /home/marxin/Programming/gcc/gcc/ipa-inline.cc:2042
0x1d972c4 ipa_inline
        /home/marxin/Programming/gcc/gcc/ipa-inline.cc:2811
0x1d972c4 execute
        /home/marxin/Programming/gcc/gcc/ipa-inline.cc:3210
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.

  reply	other threads:[~2023-05-03 11:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 11:42 [Bug ipa/109711] New: " sjames at gcc dot gnu.org
2023-05-03 11:58 ` marxin at gcc dot gnu.org [this message]
2023-05-03 12:05 ` [Bug ipa/109711] [14 regression] ICE (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in verify_range, at value-range.cc:1060) when building ffmpeg-4.4.4 since r14-377-gc92b8be9b52b7e marxin at gcc dot gnu.org
2023-05-03 12:07 ` marxin at gcc dot gnu.org
2023-05-03 12:10 ` sjames at gcc dot gnu.org
2023-05-03 13:14 ` tnfchris at gcc dot gnu.org
2023-05-03 13:15 ` rguenth at gcc dot gnu.org
2023-05-03 13:47 ` tnfchris at gcc dot gnu.org
2023-05-03 13:52 ` aldyh at gcc dot gnu.org
2023-05-03 13:52 ` aldyh at gcc dot gnu.org
2023-05-03 15:32 ` aldyh at gcc dot gnu.org
2023-05-03 17:15 ` cvs-commit at gcc dot gnu.org
2023-05-03 17:16 ` aldyh at gcc dot gnu.org
2023-11-05 21:41 ` pinskia 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-109711-4-lfcBRNBNtS@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).