public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at octaforge dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/113174] gcc fails to bootstrap on pp64le with clang-based host environment (internal compiler error)
Date: Fri, 29 Dec 2023 23:50:52 +0000	[thread overview]
Message-ID: <bug-113174-4-Q3AxkjuBPN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113174-4@http.gcc.gnu.org/bugzilla/>

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.

  parent reply	other threads:[~2023-12-29 23:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 23:33 [Bug bootstrap/113174] New: " gcc at octaforge dot org
2023-12-29 23:39 ` [Bug bootstrap/113174] " pinskia at gcc dot gnu.org
2023-12-29 23:46 ` pinskia at gcc dot gnu.org
2023-12-29 23:50 ` gcc at octaforge dot org [this message]
2023-12-29 23:53 ` gcc at octaforge dot org
2023-12-29 23:59 ` pinskia at gcc dot gnu.org
2023-12-30  0:44 ` gcc at octaforge dot org
2023-12-30 16:06 ` gcc at octaforge dot org
2024-01-07  4:24 ` gcc at octaforge dot 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-113174-4-Q3AxkjuBPN@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: link
Be 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).