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 tree-optimization/113137] New: [14 regression] Failed bootstrap with -O3 -march=znver2 Date: Mon, 25 Dec 2023 16:16:28 +0000 [thread overview] Message-ID: <bug-113137-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113137 Bug ID: 113137 Summary: [14 regression] Failed bootstrap with -O3 -march=znver2 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: tnfchris at gcc dot gnu.org Target Milestone: --- Created attachment 56936 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56936&action=edit c-cppbuiltin.ii.xz ``` # /tmp/gcc/bin/g++ -c c-cppbuiltin.ii -O3 -march=znver2 /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231224/work/gcc-14-20231224/gcc/c-family/c-cppbuiltin.cc: In function 'void builtin_define_type_minmax(const char*, const char*, tree)': /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231224/work/gcc-14-20231224/gcc/c-family/c-cppbuiltin.cc:2043:1: error: PHI node with wrong VUSE on edge from BB 12 2043 | builtin_define_type_minmax (const char *min_macro, const char *max_macro, | ^~~~~~~~~~~~~~~~~~~~~~~~~~ .MEM_218 = PHI <.MEM_59(12)> expected .MEM_191 /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231224/work/gcc-14-20231224/gcc/c-family/c-cppbuiltin.cc:2043:1: error: multiple virtual PHI nodes in BB 32 .MEM_99 = PHI <.MEM_191(14)> .MEM_217 = PHI <.MEM_59(14)> /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231224/work/gcc-14-20231224/gcc/c-family/c-cppbuiltin.cc:2043:1: error: PHI node with wrong VUSE on edge from BB 32 .MEM_103 = PHI <.MEM_217(32), .MEM_218(37)> expected .MEM_99 during GIMPLE pass: vect /var/tmp/portage/sys-devel/gcc-14.0.0_pre20231224/work/gcc-14-20231224/gcc/c-family/c-cppbuiltin.cc:2043:1: internal compiler error: verify_ssa failed Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. ``` ``` Using built-in specs. COLLECT_GCC=/tmp/gcc/bin/g++ COLLECT_LTO_WRAPPER=/tmp/gcc/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /home/sam/git/gcc/configure --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --disable-analyzer --disable-cet --disable-default-pie --disable-default-ssp --disable-gcov --disable-libada --disable-libatomic --disable-libgomp --disable-libitm --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdcxx-pch --disable-libvtv --disable-lto --disable-multilib --disable-nls --disable-objc-gc --disable-systemtap --disable-werror --enable-languages=c,c++ --prefix=/tmp/gcc --with-checking=yes,extra,rtl --without-libatomic --without-libbacktrace --without-isl --without-zstd --with-system-zlib --enable-lto --with-build-config=bootstrap-lto Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20231225 (experimental) (GCC) ```
next reply other threads:[~2023-12-25 16:16 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-25 16:16 sjames at gcc dot gnu.org [this message] 2023-12-25 16:43 ` [Bug tree-optimization/113137] " sjames at gcc dot gnu.org 2023-12-26 14:05 ` tnfchris at gcc dot gnu.org 2023-12-26 14:06 ` tnfchris at gcc dot gnu.org 2023-12-26 14:06 ` tnfchris at gcc dot gnu.org 2023-12-26 14:23 ` tnfchris at gcc dot gnu.org 2023-12-26 14:27 ` tnfchris at gcc dot gnu.org 2023-12-27 12:08 ` tnfchris at gcc dot gnu.org 2023-12-27 21:13 ` dcb314 at hotmail dot com 2023-12-28 14:27 ` tnfchris at gcc dot gnu.org 2023-12-28 18:08 ` tnfchris at gcc dot gnu.org 2023-12-29 12:16 ` tnfchris at gcc dot gnu.org 2023-12-29 13:42 ` tnfchris at gcc dot gnu.org 2023-12-29 21:06 ` tnfchris at gcc dot gnu.org 2024-01-12 9:00 ` dcb314 at hotmail dot com 2024-01-12 11:09 ` tnfchris at gcc dot gnu.org 2024-01-12 15:32 ` cvs-commit at gcc dot gnu.org 2024-01-12 15:35 ` tnfchris 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-113137-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).