Received: from mx1.mailbun.net (mx1.mailbun.net [170.39.20.100])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 167B2780FFB
	for <~alpine/devel@lists.alpinelinux.org>; Fri,  7 Jan 2022 23:28:37 +0000 (UTC)
Received: from [192.168.1.5] (unknown [172.56.6.117])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: ariadne@dereferenced.org)
	by mx1.mailbun.net (Postfix) with ESMTPSA id 9470711A60E;
	Fri,  7 Jan 2022 23:28:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dereferenced.org;
	s=mailbun; t=1641598114;
	bh=6/XHNsZs+Msts6H+iif6bCUF4MWsd8ZGndtxigZdGrI=;
	h=Date:From:To:cc:Subject:In-Reply-To:References;
	b=XGPlDEWpxhdlLSV04uY9dx+F+ZJwBn6PK3ZAUny1Up/dBVe0Uqsge4f497Wy+uTqO
	 1I7nKcY7foVB6+kcEb3RyMmCn/PBxLIDF7pbVjrhpdQTpsMgdirKyK5t1o1ACJ5Xn6
	 ApxI7OGBXaUDzTlzyPLSQiXSKKdq3709mSxXbDeacOg+ZElVcFgbsWPWnu+5zLLy9Y
	 lfeMh+h4WseXIBnNTnQNWuc4sXawCvHQgF3uOp/wZcEO/CXuLhdJHHubQ2Ve3dArVo
	 1eU2C3nN0arx7fDP3dScqjbUa2N05uD+iySu/GagVJfIF9ibaF/zLR0f78Lfso7bDm
	 AQL63nBwLD+Dw==
Date: Fri, 7 Jan 2022 17:28:24 -0600 (CST)
From: Ariadne Conill <ariadne@dereferenced.org>
To: =?ISO-8859-15?Q?S=F6ren_Tempel?= <soeren@soeren-tempel.net>
cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Thoughts on self-hosting compilers in Alpine
In-Reply-To: <2AFTQR1BCRUGG.3SMHH1I19MHLG@8pit.net>
Message-ID: <5cbbe999-af25-b85a-bd6e-4449804221ea@dereferenced.org>
References: <33KG0XO61I4IL.2Z7RTAZ5J3SY6@8pit.net> <20211122135336.4f23002c@vostro> <25NDCA56CEJST.3KSBK3JLZFOCL@8pit.net> <20211125133127.639721c9@vostro> <2AFTQR1BCRUGG.3SMHH1I19MHLG@8pit.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1437249086-1641598112=:74182"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1437249086-1641598112=:74182
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

Hi,

On Fri, 7 Jan 2022, Sören Tempel wrote:

> Hello,
>
> Little status update specifically on Go: I made some improvements to
> gccgo in the past few weeks [1, 2, 3, 4, 5, 6]. With these changes
> applied, it is now possible to bootstrap Google's Go implementation with
> gccgo on all architectures supported by Alpine [7].
>
> I also submitted a few of our libgo/gccgo related patches upstream in
> order to improve gccgo's upstream musl support [8, 9, 10]. Ideally, I
> would like to see all of our gccgo patches integrated upstream.

This is really great.  I can talk with some upstream GCC folks about 
refactoring the rest of the patchset if wanted.  I'm trying to split up 
some of our patches into logical changesets to faciitate this kind of 
upstreaming already.

> The only remaining problem I am presently aware of is that 32-bit
> architectures seem to run out-of-memory on the CI when used with
> multiple OS threads which execute user-level Go code simultaneously
> (hence bootstrapped with GOMAXPROCS=1). Nonetheless, gccgo should now be
> a viable option to bootstrap community/go if we want to go down this
> path.

This is likely due to running out of address space.  I wonder if we could 
do GOMAXPROCS="$((JOBS / 2))" and have it be fine.  Bootstrapping Go from 
gcc-go however is a welcome addition for 3.16!

Ariadne
--0-1437249086-1641598112=:74182--