public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111411] New: [14 regression] ICE when building opus-1.4 (celt_decoder.c:1182:1: internal compiler error: in extract_insn, at recog.cc:2791) Date: Thu, 14 Sep 2023 03:07:42 +0000 [thread overview] Message-ID: <bug-111411-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111411 Bug ID: 111411 Summary: [14 regression] ICE when building opus-1.4 (celt_decoder.c:1182:1: internal compiler error: in extract_insn, at recog.cc:2791) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org Target Milestone: --- Created attachment 55896 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55896&action=edit celt_decoder.c.i ``` gcc (Gentoo 14.0.0 p, commit d0b55776a4e1d2f293db5ba0e4a04aefed055ec4) 14.0.0 20230913 (experimental) 3af2af15798cb6243e2643f98f62c9270b1ca5d2 Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` ``` FAILED: celt/libopus-celt.a.p/celt_decoder.c.o aarch64-unknown-linux-gnu-gcc -Icelt/libopus-celt.a.p -Icelt -I../opus-1.4/celt -I. -I../opus-1.4 -Iinclude -I../opus-1.4/include -Isilk -I../opus-1.4/silk -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -W all -Winvalid-pch -Wextra -std=gnu99 -DOPUS_BUILD -DHAVE_CONFIG_H -fvisibility=hidden -Wcast-align -Wnested-externs -Wshadow -Wstrict-prototypes -fstack-protector-strong -O3 -pipe -mcpu=native -fdiagnostics-c olor=always -ggdb3 -fPIC -MD -MQ celt/libopus-celt.a.p/celt_decoder.c.o -MF celt/libopus-celt.a.p/celt_decoder.c.o.d -o celt/libopus-celt.a.p/celt_decoder.c.o -c ../opus-1.4/celt/celt_decoder.c ../opus-1.4/celt/celt_decoder.c: In function ‘celt_decode_with_ec’: ../opus-1.4/celt/celt_decoder.c:1182:1: error: unrecognizable insn: 1182 | } | ^ (insn 5312 42 41 42 (parallel [ (set (mem/c:SI (plus:DI (reg/f:DI 29 x29) (const_int -260 [0xfffffffffffffefc])) [18 %sfp+-260 S4 A32]) (const_int 0 [0])) (set (mem/c:SI (plus:DI (reg/f:DI 29 x29) (const_int -256 [0xffffffffffffff00])) [18 %sfp+-256 S4 A32]) (const_int 0 [0])) ]) "../opus-1.4/celt/celt_decoder.c":978:22 -1 (nil)) during RTL pass: cprop_hardreg ../opus-1.4/celt/celt_decoder.c:1182:1: internal compiler error: in extract_insn, at recog.cc:2791 0xaaaae5b09473 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /usr/src/debug/sys-devel/gcc-14.0.0.9999/gcc-14.0.0.9999/gcc/rtl-error.cc:108 0xaaaae5b0951b _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /usr/src/debug/sys-devel/gcc-14.0.0.9999/gcc-14.0.0.9999/gcc/rtl-error.cc:116 0xaaaae626d693 extract_insn(rtx_insn*) /usr/src/debug/sys-devel/gcc-14.0.0.9999/gcc-14.0.0.9999/gcc/recog.cc:2791 0xaaaae6273fb3 extract_constrain_insn(rtx_insn*) /usr/src/debug/sys-devel/gcc-14.0.0.9999/gcc-14.0.0.9999/gcc/recog.cc:2690 0xaaaae6278d5b copyprop_hardreg_forward_1 /usr/src/debug/sys-devel/gcc-14.0.0.9999/gcc-14.0.0.9999/gcc/regcprop.cc:836 0xaaaae627a7e3 execute /usr/src/debug/sys-devel/gcc-14.0.0.9999/gcc-14.0.0.9999/gcc/regcprop.cc:1423 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://bugs.gentoo.org/> for instructions. ``` gcc -c celt_decoder.c.i -O3 is enough to repro.
next reply other threads:[~2023-09-14 3:07 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-14 3:07 sjames at gcc dot gnu.org [this message] 2023-09-14 3:30 ` [Bug target/111411] " pinskia at gcc dot gnu.org 2023-09-14 3:31 ` [Bug target/111411] [14 regression] ICE when building opus-1.4, unrecognizable insn with -fstack-protector-strong pinskia at gcc dot gnu.org 2023-09-14 5:15 ` sjames at gcc dot gnu.org 2023-09-14 14:45 ` pinskia at gcc dot gnu.org 2023-09-14 15:07 ` rsandifo at gcc dot gnu.org 2023-09-14 16:33 ` sjames at gcc dot gnu.org 2023-09-14 17:34 ` rsandifo at gcc dot gnu.org 2023-09-14 18:41 ` rsandifo at gcc dot gnu.org 2023-09-14 18:41 ` rsandifo at gcc dot gnu.org 2023-09-15 8:19 ` cvs-commit at gcc dot gnu.org 2023-09-15 8:22 ` rsandifo at gcc dot gnu.org 2023-09-15 9:28 ` Martin.Jansa at gmail dot com 2023-09-15 9:28 ` Martin.Jansa at gmail dot com 2023-09-20 10:08 ` cvs-commit at gcc dot gnu.org 2023-09-20 10:13 ` cvs-commit at gcc dot gnu.org 2023-09-20 10:53 ` rsandifo at gcc dot gnu.org 2023-10-05 17:22 ` 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-111411-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).