From: Iain Sandoe <idsandoe@googlemail.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] doc: Document Solaris D bootstrap requirements [PR 103528]
Date: Wed, 16 Mar 2022 16:08:34 +0000 [thread overview]
Message-ID: <17DB28F6-968A-4717-94EA-D88E7D8D9E90@googlemail.com> (raw)
In-Reply-To: <yddpmmlhoxz.fsf@CeBiTec.Uni-Bielefeld.DE>
Hi Rainer,
> On 16 Mar 2022, at 15:55, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
>
>>> I've omitted the Darwin-specific stuff so far documented in PRs d/103577
>>> and d/103578:
>>>
>>> * needs --enable-libphobos
>>> * top of gcc-11 branch only
>>> * backport of -static-libphobos patch
>>> * Darwin/i386 doesn't work at all
>>
>> — hopefully we will not need to add that —
>>
>> The actual problem is known (FWIW there is also some wrong code generated for
>> x86_64, we just happen to link it to something harmless instead of failing
>> to link).
>
> I see. One issue I see during x86_64-darwin testing (10.7 only?) is
> that the forkgc2 test hangs and has to be killed manually.
yes, there are known issues with GC and threading - but those do not break bootstrap
since the compiler is single-threaded.
>> - I remain hopeful that a solution for 11.x can be found before gcc-12 branches,
>> since without m32 support it is hard for me to fit D into regular Darwin
>> testing (at
>> present D is effectively untested on Darwin since the change to require a D
>> bootstrap)
>> .. at one stage, D did work on m32 Darwin.
>
> 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.
Iain.
next prev parent reply other threads:[~2022-03-16 16:08 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 [this message]
2022-03-17 9:00 ` Rainer Orth
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=17DB28F6-968A-4717-94EA-D88E7D8D9E90@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).