From nobody Sat Jun 13 21:38:57 2026 X-Original-To: freebsd-ppc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gd8sR42yqz6hCYC for ; Sat, 13 Jun 2026 21:39:07 +0000 (UTC) (envelope-from pkubaj@FreeBSD.org) Received: from mail.anongoth.pl (mail.anongoth.pl [IPv6:2001:470:71:6b::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "anongoth.pl", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gd8sQ41jpz3qtQ; Sat, 13 Jun 2026 21:39:06 +0000 (UTC) (envelope-from pkubaj@FreeBSD.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=freebsd.org (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:71:6b::3 is neither permitted nor denied by domain of pkubaj@FreeBSD.org) smtp.mailfrom=pkubaj@FreeBSD.org Received: by mail.anongoth.pl (Postfix) id 36FB84164B; Sat, 13 Jun 2026 23:38:58 +0200 (CEST) Date: Sat, 13 Jun 2026 23:38:57 +0200 From: Piotr Kubaj To: Adrian Chadd Cc: freebsd-ppc@freebsd.org Subject: Re: Proposal to switch powerpc64le to IEEE-754 binary128 Message-ID: References: List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ppc@freebsd.org Sender: owner-freebsd-ppc@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FIA/wfULyNxVPOF8" Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.60 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MID_RHS_NOT_FQDN(0.50)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : No valid SPF, No valid DKIM,none]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MISSING_XM_UA(0.00)[]; FREEFALL_USER(0.00)[pkubaj]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_SPF_SOFTFAIL(0.00)[~all]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-ppc@freebsd.org]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; R_DKIM_NA(0.00)[]; TO_DN_SOME(0.00)[] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4gd8sQ41jpz3qtQ --FIA/wfULyNxVPOF8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 26-06-11 15:01:15, Adrian Chadd wrote: > On Thu, 11 Jun 2026 at 14:42, Piotr Kubaj wrote: > > > > On 26-06-11 09:54:09, Adrian Chadd wrote: > > > On Thu, 11 Jun 2026 at 01:22, Piotr Kubaj wrote: > > > > > > > > On 26-06-10 18:53:11, Adrian Chadd wrote: > > > > > So, a few of us chatted in IRC about it. > > > > > > > > > > * The minimum for PPC64LE was POWER7 anyway, right? > > > > POWER8. Last I heard, POWER7 has issues with unaligned access, whic= h is > > > > vital on LE. All the toolchains assume POWER8 as given on ppc64le. > > > > > * There's no easy way to deal with this in library versioning and > > > > > such, so we should just rip the bandaid off > > > > > * We can fix the ports as they come up. > > > > Yes, and there's not much to fix. The good news is that reinstallat= ion > > > > won't be necessary, upgrade is just the usual buildworld + installw= orld. > > > > > * people wishing to run stuff built on -15 or earlier should just= run > > > > > a userland jail. > > > > > > > > > > so given that! > > > > > > > > > > * Please include something to propose to put in UPDATING > > > > The review at https://reviews.freebsd.org/D57388 includes UPDATING > > > > entry. > > > > > * Please explain what will happen with all the toolchains in -HEA= D (eg > > > > > all the gcc versions will use the right base type, we won't have = gcc > > > > > compiling a different ABI to llvm21, etc) > > > > > > > Compilers explicitly using C's long double will need updating. > > > > Everything else will work as it is. I have tested bootstraps for Ru= st, > > > > GHC, OpenJDK and SBCL - all of them work. GCC and LLVM will need to= be > > > > updated though to emit correct long double, otherwise code built wi= th > > > > them that also uses long double type will misbehave. I'm also curre= ntly > > > > playing with ldc and it will also need to be updated. > > > > > > Ok, can you go investigate GCC and LLVM too? >=20 > > The clang part of our FreeBSD patch will be upstreamed and can be > > readily backported to our ports. >=20 > Sweet. >=20 > > > > Regarding GCC, there's a configure option for IEEE long double, so we > > would be modifying just a port's Makefile. >=20 > Sweet. >=20 > > > > > > And go, maybe? Does go currently work on ppc64le? > > > > Go doesn't work, there's a ready patch from Raptor that upstream somehow > > isn't willing to merge. Raptor is apparently working on it. I have no > > idea whether Raptor's patch will need modifications. > > > > > > > > * Let's figure out when the flag day should be. > > > > > > > Since it's CURRENT, people should expect breakages, we can't provide > > > > stability there. IMO it's better to do it sooner than later so that= more > > > > people can test it. If someone doesn't want to upgrade yet, we're n= ot > > > > Microsoft, we don't force upgrades. > > > > > > Hey if you're willing to drive it forward then great! We just need to= make sure > > > it gets done enough that we don't end up with half working toolchains= in ports. > > Hmmm, I pretty often do bulk port builds anyway, just usually not > > CURRENT, because with debugging enabled it takes a lot of time (and I > > prefer to keep it enabled because it's CURRENT). I guess after the > > switch I'll run CURRENT builds more often. >=20 > Ok. Let's pick a date and give anyone else a chance to speak up before > you pull the lever and commit us to the path! Is next Saturday 20.06 OK? >=20 >=20 >=20 > -adrian --FIA/wfULyNxVPOF8 Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQJPBAABCAA5FiEEycyIeNkkgohzsoorelmbhSCDnJ0FAmotzfEbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwyAAoJEHpZm4Ugg5ydKyoP/Ri/gAw19wRjUEqXzwMW IGeG7OpDjpr24bFncOL9GtX4ZNY/6oFcrZ4GbDTtA65jzBLFL2jLAcOg/FeLA0pg z9O3Zq7LvwCKG143XLMa4gNUTK/C4bCdDXgB8ddxQPgOSvbJeR0bLGRRh6473VuM RGK2PeWA+Orv+Ds/pITYeldTaPkdvTZuNCscp97ipzuyGL9GCptYIzcW9DKAzCJR ydBpYw9q6siX0CdOS27HMkvkOlBf7gG+XjtyD72uD/SQ89Sxp63uEaRL4+Iu70Nn 8KcvazOEugtV1slusfEA6OEwdb/MKlY/JTGJAsgQ7oHG9nB/sGsxRjRdGVfg+gvW QwuSdEpkhPjZtHgxoLupXiUiYJ2/Tbd1JNcoEUsFfSUftAlQNRwyBz/LGRW+MT2B 0lv7OhirENAiQgvRdVmUdm/iPmDnhHmifOf50Hs3mjMPHomSiwtWSVX/l0YXpcs1 k6KUcky6uvmE710aGvcHERWD13bfPQsLClXBoEBXdDU/kjh7VmcYbRv5AbyrWaZl FNwCP3tm0e+UzCnLhSB5YpuGXp+3gwgaEsoeFNuFwtmrzInI3c2ZZ6K9HynTNmT5 g7ZMVd+PeClNCfeGEz5Bui7m3jU7NJOrPz63ngNXmIGgLMCrvyHU8SF8janjrMyE wOMx1pIxZJ6+2izmdz3YS7Tf =cQu8 -----END PGP SIGNATURE----- --FIA/wfULyNxVPOF8--