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/107120] New: [13 Regression] trunk fails to bootstrap on powerpc64le-linux-gnu
Date: Sun, 02 Oct 2022 09:01:50 +0000 [thread overview]
Message-ID: <bug-107120-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107120
Bug ID: 107120
Summary: [13 Regression] trunk fails to bootstrap on
powerpc64le-linux-gnu
Product: gcc
Version: 13.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 20221001 on powerpc64le-linux-gnu, glibc 2.35, binutils 2.39:
/<<PKGBUILDDIR>>/build/gcc/include-fixed/powerpc64le-linux-gnu/bits/floatn.h:88:9:
error: multiple types in one declaration
88 | typedef __float128 _Float128;
| ^~~~~~~~~~
In file included from /usr/include/stdlib.h:56,
from
/<<PKGBUILDDIR>>/build/powerpc64le-linux-gnu/libstdc++-v3/include/cstdlib:79,
from
../../../../src/libstdc++-v3/libsupc++/atexit_thread.cc:25:
/<<PKGBUILDDIR>>/build/gcc/include-fixed/powerpc64le-linux-gnu/bits/floatn.h:88:20:
error: declaration does not declare anything [-fpermissive]
88 | typedef __float128 _Float128;
| ^~~~~~~~~
make[7]: *** [Makefile:777: atexit_thread.lo] Error 1
make[7]: Leaving directory
'/<<PKGBUILDDIR>>/build/powerpc64le-linux-gnu/libstdc++-v3/libsupc++'
make[6]: *** [Makefile:576: all-recursive] Error 1
make[6]: Leaving directory
'/<<PKGBUILDDIR>>/build/powerpc64le-linux-gnu/libstdc++-v3'
make[5]: *** [Makefile:501: all] Error 2
make[5]: Leaving directory
'/<<PKGBUILDDIR>>/build/powerpc64le-linux-gnu/libstdc++-v3'
make[4]: *** [Makefile:17947: all-stage1-target-libstdc++-v3] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[3]: *** [Makefile:31100: stage1-bubble] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[2]: *** [Makefile:31437: bootstrap] Error 2
Configured with: -v
--with-pkgversion='Debian 20221001-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-clocale=gnu
--enable-libstdcxx-debug
--enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new
--enable-gnu-unique-object
--enable-plugin
--with-system-zlib
--enable-libphobos-checking=release
--with-target-system-zlib=auto
--with-libphobos-druntime-only=yes
--enable-objc-gc=auto
--enable-secureplt
--enable-targets=powerpcle-linux
--disable-multilib
--enable-multiarch
--disable-werror
--with-long-double-128
--enable-offload-targets=nvptx-none=/<<PKGBUILDDIR>>/debian/tmp-nvptx/usr/lib/gcc-snapshot
--enable-offload-defaulted
--without-cuda-driver
--enable-checking=yes,extra,rtl
--build=powerpc64le-linux-gnu
--host=powerpc64le-linux-gnu
--target=powerpc64le-linux-gnu
next reply other threads:[~2022-10-02 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 9:01 doko at gcc dot gnu.org [this message]
2022-10-03 9:26 ` [Bug bootstrap/107120] " marxin at gcc dot gnu.org
2022-10-03 18:19 ` asolokha at gmx dot com
2022-10-06 9:55 ` rguenth at gcc dot gnu.org
2022-10-10 4:37 ` asolokha at gmx dot com
2022-10-24 8:42 ` doko 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-107120-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: 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).