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 since r14-377-gc92b8be9b52b7e Date: Wed, 03 May 2023 12:05:37 +0000 [thread overview] Message-ID: <bug-109711-4-dyzUe8Ikjk@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 ---------------------------------------------------------------------------- Keywords|needs-bisection | Summary|[14 regression] ICE (tree |[14 regression] ICE (tree |check: expected class |check: expected class |‘type’, have ‘exceptional’ |‘type’, have ‘exceptional’ |(error_mark) in |(error_mark) in |verify_range, at |verify_range, at |value-range.cc:1060) when |value-range.cc:1060) when |building ffmpeg-4.4.4 |building ffmpeg-4.4.4 since | |r14-377-gc92b8be9b52b7e --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Started with r14-377-gc92b8be9b52b7e and it's not related to aarch64, can reproduce on x86_64-linux-gnu as well.
next prev parent reply other threads:[~2023-05-03 12:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 11:42 [Bug ipa/109711] New: [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 sjames at gcc dot gnu.org 2023-05-03 11:58 ` [Bug ipa/109711] " marxin at gcc dot gnu.org 2023-05-03 12:05 ` marxin at gcc dot gnu.org [this message] 2023-05-03 12:07 ` [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: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-dyzUe8Ikjk@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).