https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113174
--- Comment #3 from Daniel Kolesa <gcc at octaforge dot org> --- this is the preprocessed source: https://0x0.st/HEt7.ii It's generated with the following command line: /builddir/gcc-13.2.1_git20231014/build/./prev-gcc/xg++ -B/builddir/gcc-13.2.1_git20231014/build/./prev-gcc/ -B/usr/powerpc64le-chimera-linux-musl/bin/ -nostdinc++ -B/builddir/gcc-13.2.1_git20231014/build/prev-powerpc64le-chimera-linux-musl/libstdc++-v3/src/.libs -B/builddir/gcc-13.2.1_git20231014/build/prev-powerpc64le-chimera-linux-musl/libstdc++-v3/libsupc++/.libs -I/builddir/gcc-13.2.1_git20231014/build/prev-powerpc64le-chimera-linux-musl/libstdc++-v3/include/powerpc64le-chimera-linux-musl -I/builddir/gcc-13.2.1_git20231014/build/prev-powerpc64le-chimera-linux-musl/libstdc++-v3/include -I/builddir/gcc-13.2.1_git20231014/libstdc++-v3/libsupc++ -L/builddir/gcc-13.2.1_git20231014/build/prev-powerpc64le-chimera-linux-musl/libstdc++-v3/src/.libs -L/builddir/gcc-13.2.1_git20231014/build/prev-powerpc64le-chimera-linux-musl/libstdc++-v3/libsupc++/.libs -fno-PIE -c -g -O2 -fno-checking -fno-tree-ter -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Wconditionally-supported -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I/builddir/gcc-13.2.1_git20231014/gcc -I/builddir/gcc-13.2.1_git20231014/gcc/. -I/builddir/gcc-13.2.1_git20231014/gcc/../include -I/builddir/gcc-13.2.1_git20231014/gcc/../libcpp/include -I/builddir/gcc-13.2.1_git20231014/gcc/../libcody -Iyes/include -Iyes/include -Iyes/include -I/builddir/gcc-13.2.1_git20231014/gcc/../libdecnumber -I/builddir/gcc-13.2.1_git20231014/gcc/../libdecnumber/dpd -I../libdecnumber -I/builddir/gcc-13.2.1_git20231014/gcc/../libbacktrace -o modulo-sched.o -MT modulo-sched.o -MMD -MP -MF ./.deps/modulo-sched.TPo /builddir/gcc-13.2.1_git20231014/gcc/modulo-sched.cc The command line is taken from the failing log. Yes, it could be an LLVM bug. It's hard to say whether it is though.
