public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107059] New: [13 regression] bootstrap failure after r13-2887-gb04208895fed34
Date: Tue, 27 Sep 2022 16:46:04 +0000 [thread overview]
Message-ID: <bug-107059-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059
Bug ID: 107059
Summary: [13 regression] bootstrap failure after
r13-2887-gb04208895fed34
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:b04208895fed34171eac6bafb60c90048eb1cb0c, r13-2887-gb04208895fed34
Which doing a bootstrap (during stage 1) I get the following sorts of errors
after this commit.
/bin/bash ../libtool --tag CXX --tag disable-shared --mode=compile
/home/seurer/gcc/git/build/gcc-test/./gcc/xgcc -shared-libgcc
-B/home/seurer/gcc/git/build/gcc-test/./gcc -nostdinc++
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/src
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/src/.libs
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/bin/
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/lib/
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/include
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/sys-include
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/../libgcc
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/powerpc64le-unknown-linux-gnu
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++ -prefer-pic
-D_GLIBCXX_SHARED -fno-implicit-templates -Wall -Wextra -Wwrite-strings
-Wcast-qual -Wabi=2 -fdiagnostics-show-location=once -ffunction-sections
-fdata-sections -frandom-seed=atexit_thread.lo -mno-gnu-attribute -g -O2
-D_GNU_SOURCE -c -o atexit_thread.lo
/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++/atexit_thread.cc
libtool: compile: /home/seurer/gcc/git/build/gcc-test/./gcc/xgcc
-shared-libgcc -B/home/seurer/gcc/git/build/gcc-test/./gcc -nostdinc++
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/src
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/src/.libs
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/bin/
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/lib/
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/include
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/sys-include
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/../libgcc
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/powerpc64le-unknown-linux-gnu
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++ -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi=2
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=atexit_thread.lo -mno-gnu-attribute -g -O2 -D_GNU_SOURCE -c
/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++/atexit_thread.cc -fPIC
-DPIC -D_GLIBCXX_SHARED -o atexit_thread.o
/usr/include/powerpc64le-linux-gnu/bits/floatn.h:79:9: error: multiple types in
one declaration
79 | typedef __float128 _Float128;
| ^~~~~~~~~~
In file included from /usr/include/stdlib.h:56,
from
/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/cstdlib:79,
from
/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++/atexit_thread.cc:25:
/usr/include/powerpc64le-linux-gnu/bits/floatn.h:79:20: error: declaration does
not declare anything [-fpermissive]
79 | typedef __float128 _Float128;
| ^~~~~~~~~
In file included from /usr/include/powerpc64le-linux-gnu/bits/floatn.h:120:
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:214:9: error: multiple
types in one declaration
214 | typedef float _Float32;
| ^~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:214:15: error:
declaration does not declare anything [-fpermissive]
214 | typedef float _Float32;
| ^~~~~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:251:9: error: multiple
types in one declaration
251 | typedef double _Float64;
| ^~~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:251:16: error:
declaration does not declare anything [-fpermissive]
251 | typedef double _Float64;
| ^~~~~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:268:9: error: multiple
types in one declaration
268 | typedef double _Float32x;
| ^~~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:268:16: error:
declaration does not declare anything [-fpermissive]
268 | typedef double _Float32x;
| ^~~~~~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:298:9: error: multiple
types in one declaration
298 | typedef _Float128 _Float64x;
| ^~~~~~~~~
/usr/include/powerpc64le-linux-gnu/bits/floatn-common.h:298:19: error:
declaration does not declare anything [-fpermissive]
298 | typedef _Float128 _Float64x;
| ^~~~~~~~~
commit b04208895fed34171eac6bafb60c90048eb1cb0c (HEAD)
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Sep 27 08:04:06 2022 +0200
c++: Implement P1467R9 - Extended floating-point types and standard names
compiler part except for bfloat16 [PR106652]
next reply other threads:[~2022-09-27 16:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 16:46 seurer at gcc dot gnu.org [this message]
2022-09-27 17:10 ` [Bug bootstrap/107059] " jakub at gcc dot gnu.org
2022-09-27 17:28 ` marxin at gcc dot gnu.org
2022-09-27 17:37 ` jakub at gcc dot gnu.org
2022-09-27 18:40 ` seurer at gcc dot gnu.org
2022-09-27 18:50 ` jakub at gcc dot gnu.org
2022-09-27 18:52 ` seurer at gcc dot gnu.org
2022-09-27 19:13 ` jakub at gcc dot gnu.org
2022-09-27 19:20 ` seurer at gcc dot gnu.org
2022-09-27 19:26 ` jakub at gcc dot gnu.org
2022-09-27 19:59 ` seurer at gcc dot gnu.org
2022-09-27 20:22 ` jakub at gcc dot gnu.org
2022-09-28 9:45 ` tnfchris at gcc dot gnu.org
2022-09-28 9:46 ` jakub at gcc dot gnu.org
2022-09-28 10:12 ` jakub at gcc dot gnu.org
2022-09-28 10:59 ` burnus at gcc dot gnu.org
2022-09-28 11:18 ` burnus at gcc dot gnu.org
2022-09-28 11:26 ` burnus at gcc dot gnu.org
2022-09-28 11:37 ` jakub at gcc dot gnu.org
2022-09-28 12:58 ` burnus at gcc dot gnu.org
2022-09-28 13:10 ` burnus at gcc dot gnu.org
2022-09-28 13:12 ` jakub at gcc dot gnu.org
2022-09-28 17:16 ` joseph at codesourcery dot com
2022-09-28 18:40 ` burnus at gcc dot gnu.org
2022-09-28 18:47 ` jakub at gcc dot gnu.org
2022-09-28 18:57 ` burnus at gcc dot gnu.org
2022-09-28 19:04 ` jakub at gcc dot gnu.org
2022-09-28 19:20 ` manuel.lauss at googlemail dot com
2022-09-29 8:07 ` rguenth at gcc dot gnu.org
2022-09-29 10:06 ` cvs-commit at gcc dot gnu.org
2022-09-29 10:14 ` jakub at gcc dot gnu.org
2022-10-03 15:29 ` seurer at gcc dot gnu.org
2022-10-03 15:33 ` jakub at gcc dot gnu.org
2022-10-07 7:00 ` cvs-commit at gcc dot gnu.org
2022-10-07 7:00 ` cvs-commit at gcc dot gnu.org
2022-10-07 7:01 ` jakub 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-107059-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).