public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris 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 13:14:26 +0000 [thread overview]
Message-ID: <bug-109711-4-CrxiTN2uXd@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
--- Comment #5 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #3)
> Hm, on x86_64-linux-gnu, it started with r13-6616-g2246d576f922ba.
$ cat prtest2.c
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);
}
$ ./install/bin/gcc --version
gcc (GCC) 13.0.1 20230312 (experimental)
$ git log -1
commit 2246d576f922bae3629da0fe1dbfcc6ff06769ad (HEAD)
Author: Tamar Christina <tamar.christina@arm.com>
Date: Sun Mar 12 18:39:33 2023 +0000
middle-end: Revert can_special_div_by_const changes [PR108583]
This reverts the changes for the CAN_SPECIAL_DIV_BY_CONST hook.
gcc/ChangeLog:
PR target/108583
* doc/tm.texi (TARGET_VECTORIZE_CAN_SPECIAL_DIV_BY_CONST): Remove.
* doc/tm.texi.in: Likewise.
* explow.cc (round_push, align_dynamic_address): Revert previous
patch.
* expmed.cc (expand_divmod): Likewise.
* expmed.h (expand_divmod): Likewise.
* expr.cc (force_operand, expand_expr_divmod): Likewise.
* optabs.cc (expand_doubleword_mod, expand_doubleword_divmod):
Likewise.
* target.def (can_special_div_by_const): Remove.
* target.h: Remove tree-core.h include
* targhooks.cc (default_can_special_div_by_const): Remove.
* targhooks.h (default_can_special_div_by_const): Remove.
* tree-vect-generic.cc (expand_vector_operation): Remove hook.
* tree-vect-patterns.cc (vect_recog_divmod_pattern): Remove hook.
* tree-vect-stmts.cc (vectorizable_operation): Remove hook.
$ ./install/bin/gcc -O2 -S -o - prtest2.c
.file "prtest2.c"
.text
.p2align 4
.globl interpolate_lpc
.type interpolate_lpc, @function
interpolate_lpc:
.LFB0:
.cfi_startproc
movl interpolate_lpc_q_0(%rip), %eax
testl %eax, %eax
je .L1
pxor %xmm0, %xmm0
cvtsi2ssl %edi, %xmm0
ucomiss .LC0(%rip), %xmm0
jp .L4
jne .L4
.L1:
ret
.p2align 4,,10
.p2align 3
...
Also that commit doesn't build because I forgot to cp tm.texi to the source
directory after the revert.
So I think the bisect probably didn't find it in that range.
https://godbolt.org/z/r44xGzarY indicates GCC 13.1 is fine. So I don't think
this one is mine.
next prev parent reply other threads:[~2023-05-03 13:14 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 ` [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 [this message]
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-CrxiTN2uXd@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).