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 other/111559] [14 regression] ICE when building Python with PGO Date: Sat, 23 Sep 2023 21:48:50 +0000 [thread overview] Message-ID: <bug-111559-4-k9afoo4kHm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111559-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111559 --- Comment #1 from Sam James <sjames at gcc dot gnu.org> --- I don't think I'm going to be able to get a minimal reproducer for this, but trying to at least get something a bit smaller/precise. If I take inspiration from PR79587, I can do a bit better: * wget https://www.python.org/ftp/python/3.11.5/Python-3.11.5.tar.xz * tar xvf Python-3.11.5.tar.xz * ./configure CC=gcc-14 --enable-optimizations * make clean * make profile-removal * make build_all_generate_profile * make profile-removal * make run_profile_task # unfortunately this runs something like 44 different Python tests * make build_all_merge_profile * gcc-14 -c -fno-strict-overflow -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -fwrapv -fno-semantic-interposition -std=c11 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wstrict-prototypes -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-use -fprofile-correction -I./Include/internal -I. -I./Include -I/usr/include/ncursesw -fPIC -DPy_BUILD_CORE -o Parser/parser.o Parser/parser.c -save-temps ``` gcc-14 -c -fno-strict-overflow -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -pipe -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -fwrapv -fno-semantic-interposition -std=c11 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wstrict-prototypes -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-use -fprofile-correction -I./Include/internal -I. -I./Include -I/usr/include/ncursesw -fPIC -DPy_BUILD_CORE -o Parser/parser.o Parser/parser.c -save-temps gcc-14: warning: ‘-pipe’ ignored because ‘-save-temps’ specified Parser/parser.c: In function ‘_tmp_28_rule’: Parser/parser.c:25179:1: error: probability of edge 3->4 not initialized 25179 | _tmp_28_rule(Parser *p) | ^~~~~~~~~~~~ Parser/parser.c:25179:1: error: probability of edge 5->11 not initialized during GIMPLE pass: fixup_cfg Parser/parser.c:25179:1: internal compiler error: verify_flow_info failed 0x55b70ce37153 verify_flow_info() /usr/src/debug/sys-devel/gcc-14.0.0_pre20230917/gcc-14-20230917/gcc/cfghooks.cc:287 0x55b70d295897 execute_function_todo /usr/src/debug/sys-devel/gcc-14.0.0_pre20230917/gcc-14-20230917/gcc/passes.cc:2100 0x55b70d295e10 execute_todo /usr/src/debug/sys-devel/gcc-14.0.0_pre20230917/gcc-14-20230917/gcc/passes.cc:2142 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-14 -v Using built-in specs. COLLECT_GCC=gcc-14 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/14/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-14.0.0_pre20230917/work/gcc-14-20230917/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/14 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/14/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/14 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/14/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/14/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/14/include/g++-v14 --disable-silent-rules --disable-dependency-tracking --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/14/python --enable-languages=c,c++,fortran,rust --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --disable-libunwind-exceptions --enable-checking=yes,extra,rtl --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo Hardened 14.0.0_pre20230917 p2' --with-gcc-major-version-only --enable-libstdcxx-time --enable-lto --disable-libstdcxx-pch --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-fixed-point --enable-targets=all --enable-libgomp --disable-libssp --disable-libada --enable-cet --disable-systemtap --enable-valgrind-annotations --disable-vtable-verify --disable-libvtv --with-zstd --with-isl --disable-isl-version-check --enable-default-pie --enable-host-pie --enable-host-bind-now --enable-default-ssp --with-build-config=bootstrap-cet Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.0 20230917 (experimental) (Gentoo Hardened 14.0.0_pre20230917 p2) ``` I've uploaded build dir after running that last command at https://dev.gentoo.org/~sam/bugs/gcc/gcc-python-pgo-x86/Python-3.11.5-pgo-crash.tar.xz.
next prev parent reply other threads:[~2023-09-23 21:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-23 21:42 [Bug other/111559] New: " sjames at gcc dot gnu.org 2023-09-23 21:48 ` sjames at gcc dot gnu.org [this message] 2023-09-23 21:49 ` [Bug gcov-profile/111559] " pinskia at gcc dot gnu.org 2023-09-24 9:03 ` slyfox at gcc dot gnu.org 2023-09-24 9:15 ` sirl at gcc dot gnu.org 2023-09-27 8:03 ` slyfox at gcc dot gnu.org 2023-09-27 8:11 ` slyfox at gcc dot gnu.org 2023-09-27 13:21 ` slyfox at gcc dot gnu.org 2023-09-27 14:46 ` slyfox at gcc dot gnu.org 2023-09-28 14:17 ` sirl at gcc dot gnu.org 2023-10-05 16:14 ` cvs-commit at gcc dot gnu.org 2023-10-05 16:16 ` slyfox 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-111559-4-k9afoo4kHm@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).