Date: Sat, 08 Jan 2022 15:23:36 +0100
To: Ariadne Conill <ariadne@dereferenced.org>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Thoughts on self-hosting compilers in Alpine
From: =?UTF-8?Q?S=C3=B6ren?= Tempel <soeren@soeren-tempel.net>
References: <33KG0XO61I4IL.2Z7RTAZ5J3SY6@8pit.net>
 <20211122135336.4f23002c@vostro> <25NDCA56CEJST.3KSBK3JLZFOCL@8pit.net>
 <20211125133127.639721c9@vostro> <2AFTQR1BCRUGG.3SMHH1I19MHLG@8pit.net>
 <5cbbe999-af25-b85a-bd6e-4449804221ea@dereferenced.org>
In-Reply-To: <5cbbe999-af25-b85a-bd6e-4449804221ea@dereferenced.org>
Message-Id: <2T2YXO70Z10J1.3W1PF2WCBIADU@8pit.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ariadne Conill <ariadne@dereferenced.org> wrote:
> I can talk with some upstream GCC folks about refactoring the rest of
> the patchset if wanted.

Sure, if you are in touch with any GCC developers that could help us
refactor our patches in order to get them integrated upstream that would
much appreciated.

> I'm trying to split up some of our patches into logical changesets to
> faciitate this kind of upstreaming already.

Great! Let me know if I can be of assistance.

> This is likely due to running out of address space. I wonder if we could=20=

> do GOMAXPROCS=3D"$((JOBS / 2))" and have it be fine.

Yes, GOMAXPROCS=3D$((JOBS / 2)) may also work. Nonetheless, this needs
some further investigation since I don't really understand why Go would
run out of address space with certain GOMAXPROCS values on 32-bit
architectures. However, for now just limiting GOMAXPROCS should be fine.

Greetings,
S=C3=B6ren