public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/111601] New: [14 Regression] bootstrap fails in stagestrain in libcody on x86_64-linux-gnu and powerpc64le-linux-gnu Date: Tue, 26 Sep 2023 15:27:40 +0000 [thread overview] Message-ID: <bug-111601-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111601 Bug ID: 111601 Summary: [14 Regression] bootstrap fails in stagestrain in libcody on x86_64-linux-gnu and powerpc64le-linux-gnu Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: doko at gcc dot gnu.org Target Milestone: --- seen with trunk 20230917 and 20230926 on both x86_64-linux-gnu and powerpc64le-linux-gnu with a profiled lto build. last successful build with this configuration was 20230907. not seen on aarch64, s390x, riscv64. build/libcody/config.log just shows: onfigure:2143: checking whether the C++ compiler works configure:2165: /home/packages/gcc/snap/gcc-snapshot-20230917/build/./prev-gcc/xg++ -B/home/packages/gcc/snap/gcc-snapshot-20230917/build/./prev-gcc/ -B/usr/lib/gcc-snapshot/x86_64-linux-gnu/bin/ -nostdinc++ -B/home/packages/gcc/snap/gcc-snapshot-20230917/build/prev-x86_64-linux-gnu/libstdc++-v3/src/.libs -B/home/packages/gcc/snap/gcc-snapshot-20230917/build/prev-x86_64-linux-gnu/libstdc++-v3/libsupc++/.libs -isystem /home/packages/gcc/snap/gcc-snapshot-20230917/build/prev-x86_64-linux-gnu/libstdc++-v3/include/x86_64-linux-gnu -isystem /home/packages/gcc/snap/gcc-snapshot-20230917/build/prev-x86_64-linux-gnu/libstdc++-v3/include -isystem /home/packages/gcc/snap/gcc-snapshot-20230917/src/libstdc++-v3/libsupc++ -L/home/packages/gcc/snap/gcc-snapshot-20230917/build/prev-x86_64-linux-gnu/libstdc++-v3/src/.libs -L/home/packages/gcc/snap/gcc-snapshot-20230917/build/prev-x86_64-linux-gnu/libstdc++-v3/libsupc++/.libs -g -O2 -static-libstdc++ -static-libgcc -Wl,-z,relro conftest.cpp >&5 xg++: internal compiler error: Segmentation fault signal terminated program cc1plus Please submit a full bug report, with preprocessed source (by using -freport-bug). See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions. configure:2169: $? = 4 configure:2207: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "codylib" | #define PACKAGE_TARNAME "codylib" | #define PACKAGE_VERSION "0.0" | #define PACKAGE_STRING "codylib 0.0" | #define PACKAGE_BUGREPORT "github.com/urnathan/libcody" | #define PACKAGE_URL "" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:2212: error: in `/home/packages/gcc/snap/gcc-snapshot-20230917/build/libcody': configure:2214: error: C++ compiler cannot create executables GCC is configured with Configured with: -v --with-pkgversion='Debian 20230926-1' --with-bugurl='file:///usr/share/doc/gcc-snapshot/README.Bugs' --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr/lib/gcc-snapshot --with-gcc-major-version-only --program-prefix= --enable-shared --enable-linker-build-id --disable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/<<PKGBUILDDIR>>/debian/tmp-nvptx/usr/lib/gcc-snapshot,amdgcn-amdhsa=/<<PKGBUILDDIR>>/debian/tmp-gcn/usr/lib/gcc-snapshot --enable-offload-defaulted --without-cuda-driver --enable-checking=yes,extra,rtl --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=3 and running make profiledbootstrap-lean
next reply other threads:[~2023-09-26 15:27 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-26 15:27 doko at gcc dot gnu.org [this message] 2023-09-26 17:15 ` [Bug bootstrap/111601] " pinskia at gcc dot gnu.org 2023-10-17 2:11 ` bergner at gcc dot gnu.org 2023-10-18 13:31 ` doko at gcc dot gnu.org 2023-10-18 19:48 ` bergner at gcc dot gnu.org 2023-10-18 20:41 ` bergner at gcc dot gnu.org 2023-10-18 20:53 ` pinskia at gcc dot gnu.org 2023-10-18 21:26 ` bergner at gcc dot gnu.org 2023-10-19 6:23 ` rguenth at gcc dot gnu.org 2023-11-17 5:33 ` jeevitha at gcc dot gnu.org 2023-11-24 19:59 ` jakub at gcc dot gnu.org 2023-11-26 21:36 ` [Bug bootstrap/111601] [14 Regression] profilebootstrap " jakub at gcc dot gnu.org 2023-11-27 11:37 ` jakub at gcc dot gnu.org 2023-11-27 12:24 ` rguenther at suse dot de 2023-11-27 12:27 ` jakub at gcc dot gnu.org 2023-11-27 13:31 ` jakub at gcc dot gnu.org 2023-11-27 13:51 ` jakub at gcc dot gnu.org 2023-11-27 15:14 ` jakub at gcc dot gnu.org 2023-11-27 16:21 ` jakub at gcc dot gnu.org 2023-11-27 16:45 ` jakub at gcc dot gnu.org 2023-11-27 16:57 ` jakub at gcc dot gnu.org 2023-11-27 17:01 ` jakub at gcc dot gnu.org 2023-11-27 18:33 ` jakub at gcc dot gnu.org 2023-11-27 19:24 ` jakub at gcc dot gnu.org 2023-11-27 20:02 ` jakub at gcc dot gnu.org 2023-11-27 20:17 ` jakub at gcc dot gnu.org 2023-11-29 8:18 ` cvs-commit at gcc dot gnu.org 2023-11-29 8:31 ` jakub at gcc dot gnu.org 2023-11-30 17:20 ` jeevitha 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-111601-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).