public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/97504] [11 Regression] Ada bootstrap error after r11-4029
Date: Fri, 30 Oct 2020 08:42:38 +0000 [thread overview]
Message-ID: <bug-97504-4-p0l7gtK8jB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97504-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97504
--- Comment #25 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #23)
> > It's a build log from OpenSUSE OBS, so it contains all that you requested.
>
> AFAICS this log is for a native compiler:
>
> [ 131s] checking build system type... powerpc64-suse-linux-gnu
> [ 131s] checking host system type... powerpc64-suse-linux-gnu
> [ 131s] checking target system type... powerpc64-suse-linux-gnu
>
> but I gather that --with-cpu=default32 somehow forces it to default to
> 32-bit, making it really powerpc-suse-linux-gnu under the hood? Again this
> Debian-like abomination if you ask me, which probably fools the logic in
> Makefile.rtl.
Yes, we're building a 64bit compiler defaulting to -m32. Our
"ppc" target was never a true 32bit system but a 64bit system with a
32bit "default" runtime and 64bit multilibs, so most binaries in the
system were 32bit binaries but select ones could be 64bit.
Note the GCC binaries themselves become 32bit binaries as well (the way
we use it the host compiler is the very same, powerpc64-linux compiler
defaulting to 32bit code generation).
For "ppc64" this infrastructure is also used to build 32bit runtimes
for packages that do not multilib themselves (so we cannot really abandone
it completely).
next prev parent reply other threads:[~2020-10-30 8:42 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 15:21 [Bug ada/97504] New: [11 regress] " seurer at gcc dot gnu.org
2020-10-20 15:29 ` [Bug ada/97504] " schwab@linux-m68k.org
2020-10-21 6:07 ` [Bug ada/97504] [11 Regression] " rguenth at gcc dot gnu.org
2020-10-21 8:48 ` stefansf at linux dot ibm.com
2020-10-22 18:15 ` ebotcazou at gcc dot gnu.org
2020-10-23 6:14 ` aoliva at gcc dot gnu.org
2020-10-23 6:21 ` aoliva at gcc dot gnu.org
2020-10-23 9:39 ` cvs-commit at gcc dot gnu.org
2020-10-23 9:43 ` aoliva at gcc dot gnu.org
2020-10-23 9:50 ` stefansf at linux dot ibm.com
2020-10-24 14:26 ` schwab@linux-m68k.org
2020-10-24 14:56 ` seurer at gcc dot gnu.org
2020-10-27 10:21 ` marxin at gcc dot gnu.org
2020-10-27 10:33 ` ebotcazou at gcc dot gnu.org
2020-10-27 12:31 ` ebotcazou at gcc dot gnu.org
2020-10-27 12:35 ` seurer at gcc dot gnu.org
2020-10-27 14:51 ` marxin at gcc dot gnu.org
2020-10-27 17:46 ` ebotcazou at gcc dot gnu.org
2020-10-28 3:23 ` aoliva at gcc dot gnu.org
2020-10-28 10:56 ` cvs-commit at gcc dot gnu.org
2020-10-29 9:37 ` marxin at gcc dot gnu.org
2020-10-29 9:37 ` marxin at gcc dot gnu.org
2020-10-29 9:37 ` marxin at gcc dot gnu.org
2020-10-29 9:38 ` marxin at gcc dot gnu.org
2020-10-29 11:45 ` ebotcazou at gcc dot gnu.org
2020-10-29 18:26 ` marxin at gcc dot gnu.org
2020-10-30 8:42 ` rguenth at gcc dot gnu.org [this message]
2020-10-30 10:10 ` ebotcazou at gcc dot gnu.org
2020-10-30 13:48 ` ebotcazou at gcc dot gnu.org
2020-11-05 16:24 ` marxin at gcc dot gnu.org
2020-11-05 16:25 ` marxin at gcc dot gnu.org
2020-11-05 16:57 ` ebotcazou at gcc dot gnu.org
2020-11-05 16:58 ` ebotcazou at gcc dot gnu.org
2020-11-06 10:01 ` marxin at gcc dot gnu.org
2020-11-19 14:57 ` danglin at gcc dot gnu.org
2020-11-20 14:01 ` danglin at gcc dot gnu.org
2020-11-27 12:53 ` marxin at gcc dot gnu.org
2020-11-27 13:20 ` ebotcazou at gcc dot gnu.org
2020-11-27 16:20 ` danglin at gcc dot gnu.org
2020-11-29 15:58 ` cvs-commit at gcc dot gnu.org
2020-12-03 18:53 ` ebotcazou at gcc dot gnu.org
2020-12-04 8:16 ` ebotcazou at gcc dot gnu.org
2020-12-07 8:41 ` cvs-commit at gcc dot gnu.org
2020-12-17 8:24 ` glaubitz at physik dot fu-berlin.de
2021-01-14 9:28 ` rguenth at gcc dot gnu.org
2021-01-14 9:30 ` marxin at gcc dot gnu.org
2021-01-14 9:45 ` doko at debian dot org
2021-01-14 10:10 ` marxin at gcc dot gnu.org
2022-02-13 22:58 ` cvs-commit at gcc dot gnu.org
2022-02-13 23:01 ` cvs-commit at gcc dot gnu.org
2022-02-13 23:03 ` macro at orcam dot me.uk
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-97504-4-p0l7gtK8jB@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).