public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thomas.petazzoni@free-electrons.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106972] New: internal compiler error: in extract_insn, at recog.c:2770 on ARMeb when building gcc itself Date: Tue, 20 Sep 2022 06:24:19 +0000 [thread overview] Message-ID: <bug-106972-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106972 Bug ID: 106972 Summary: internal compiler error: in extract_insn, at recog.c:2770 on ARMeb when building gcc itself Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: thomas.petazzoni@free-electrons.com Target Milestone: --- When building gcc 11.3.0 for armeb, with the following configure command line: (cd /home/thomas/autobuild/instance-1/output-1/build/host-gcc-initial-11.3.0/build && rm -rf config.cache; PATH="/home/thomas/autobuild/instance-1/output-1/host/bin:/home/thomas/autobuild/instance-1/output-1/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" PKG_CONFIG="/home/thomas/autobuild/instance-1/output-1/host/bin/pkg-config" PKG_CONFIG_SYSROOT_DIR="/" PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_LIBDIR="/home/thomas/autobuild/instance-1/output-1/host/lib/pkgconfig:/home/thomas/autobuild/instance-1/output-1/host/share/pkgconfig" AR="/usr/bin/ar" AS="/usr/bin/as" LD="/usr/bin/ld" NM="/usr/bin/nm" CC="/usr/bin/gcc" GCC="/usr/bin/gcc" CXX="/usr/bin/g++" CPP="/usr/bin/cpp" OBJCOPY="/usr/bin/objcopy" RANLIB="/usr/bin/ranlib" CPPFLAGS="-I/home/thomas/autobuild/instance-1/output-1/host/include" CFLAGS="-O2 -I/home/thomas/autobuild/instance-1/output-1/host/include" CXXFLAGS="-O2 -I/home/thomas/autobuild/instance-1/output-1/host/include" LDFLAGS="-L/home/thomas/autobuild/instance-1/output-1/host/lib -Wl,-rpath,/home/thomas/autobuild/instance-1/output-1/host/lib" INTLTOOL_PERL=/usr/bin/perl CFLAGS="-O2 -I/home/thomas/autobuild/instance-1/output-1/host/include" LDFLAGS="-L/home/thomas/autobuild/instance-1/output-1/host/lib -Wl,-rpath,/home/thomas/autobuild/instance-1/output-1/host/lib" MAKEINFO=missing CFLAGS_FOR_TARGET="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g0 -D_FORTIFY_SOURCE=1" CXXFLAGS_FOR_TARGET="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g0 -D_FORTIFY_SOURCE=1" AR_FOR_TARGET=gcc-ar NM_FOR_TARGET=gcc-nm RANLIB_FOR_TARGET=gcc-ranlib CONFIG_SITE=/dev/null ./configure --prefix="/home/thomas/autobuild/instance-1/output-1/host" --sysconfdir="/home/thomas/autobuild/instance-1/output-1/host/etc" --localstatedir="/home/thomas/autobuild/instance-1/output-1/host/var" --enable-shared --disable-static --disable-gtk-doc --disable-gtk-doc-html --disable-doc --disable-docs --disable-documentation --disable-debug --with-xmlto=no --with-fop=no --disable-nls --disable-dependency-tracking --target=armeb-buildroot-linux-gnueabi --with-sysroot=/home/thomas/autobuild/instance-1/output-1/host/armeb-buildroot-linux-gnueabi/sysroot --enable-__cxa_atexit --with-gnu-ld --disable-libssp --disable-multilib --disable-decimal-float --enable-plugins --enable-lto --with-gmp=/home/thomas/autobuild/instance-1/output-1/host --with-mpc=/home/thomas/autobuild/instance-1/output-1/host --with-mpfr=/home/thomas/autobuild/instance-1/output-1/host --with-pkgversion="Buildroot 2022.08-rc1-468-g0f42b81532" --with-bugurl="http://bugs.buildroot.net/" --without-zstd --disable-libquadmath --disable-libquadmath-support --enable-tls --enable-threads --without-isl --without-cloog --with-float=soft --with-abi="aapcs-linux" --with-cpu=iwmmxt --with-float=soft --with-mode=arm --enable-languages=c --disable-shared --without-headers --disable-threads --with-newlib --disable-largefile ) The build fails with: ../../../libgcc/config/arm/unwind-arm.c:467:1: error: unrecognizable insn: 467 | } | ^ (insn 2 4 3 2 (set (reg/v/f:SI 118 [ p ]) (reg:SI 0 r0 [ p ])) "../../../libgcc/config/arm/unwind-arm.c":456:1 -1 (nil)) during RTL pass: vregs ../../../libgcc/config/arm/unwind-arm.c:467:1: internal compiler error: in extract_insn, at recog.c:2770 (The same error happens in several place) Full build log at http://autobuild.buildroot.net/results/8e4c4512902c34d8ec0c6f8dfff92b7a198e4b4a/build-end.log There are a number of similar reports, but they don't seem to apply: - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99724 is already fixed in gcc 11.3.0 - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102222 is S390 specific
next reply other threads:[~2022-09-20 6:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 6:24 thomas.petazzoni@free-electrons.com [this message] 2022-09-20 6:32 ` [Bug target/106972] " pinskia at gcc dot gnu.org 2022-09-20 6:48 ` thomas.petazzoni@free-electrons.com 2022-09-20 6:54 ` pinskia at gcc dot gnu.org 2022-09-20 14:52 ` rearnsha at gcc dot gnu.org 2022-09-20 15:00 ` thomas.petazzoni@free-electrons.com 2022-09-20 15:10 ` rearnsha at gcc dot gnu.org 2022-09-25 19:43 ` thomas.petazzoni@free-electrons.com
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-106972-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).