From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] doc: Document Solaris D bootstrap requirements [PR 103528]
Date: Thu, 17 Mar 2022 10:00:32 +0100 [thread overview]
Message-ID: <yddh77xgdhr.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <17DB28F6-968A-4717-94EA-D88E7D8D9E90@googlemail.com> (Iain Sandoe's message of "Wed, 16 Mar 2022 16:08:34 +0000")
Hi Iain,
>> I suspected that the 32-bit issue might be due to several stdint types
>> being wrong, which was just fixed on master. At least the issue seemed
>> similar to PR d/104738. I'm building a 64-bit trunk gdc as we speak in
>> order to try that as a bootstrap compiler for a 32-bit build.
>
> The issue on 11.x is related to code that tries to synthesize section-start
> symbols, it causes a link fail on m32 - which is a bootstrap breaker.
>
> .. if that has been fixed for m32 codegenon master then, yes - presumably we
> could build an x86_64 compiler and use that “-m32” to make an i686 bootstrap.
I tried just that: 64-bit-default gdc 12.0.1 as of 20220311 as bootstrap
compiler with -m32 for i386-apple-darwin11.4.2 target: same link
failures, unfortunately.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-03-17 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 13:28 Rainer Orth
2022-03-16 15:45 ` Iain Sandoe
2022-03-16 15:55 ` Rainer Orth
2022-03-16 16:08 ` Iain Sandoe
2022-03-17 9:00 ` Rainer Orth [this message]
2022-03-30 10:37 ` Rainer Orth
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=yddh77xgdhr.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
/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).