From nobody Thu Jun 11 16:54:09 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 4gbpdq2pg7z6hsFH for ; Thu, 11 Jun 2026 16:54:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qk1-f171.google.com (mail-qk1-f171.google.com [209.85.222.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gbpdp5338z4182 for ; Thu, 11 Jun 2026 16:54:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-f171.google.com with SMTP id af79cd13be357-9156b74006aso8087985a.0 for ; Thu, 11 Jun 2026 09:54:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1781196862; cv=none; d=google.com; s=arc-20240605; b=ILvo8sEDPyJ5+e8V5xk9siV53LoGRmmJaUOtbEyCo9c5HMrBlLjUETc6c46nd6GFoM 2d5H9A4yqGuH21CHHVpwOlYzymWDmM4NhNeRtnYXQTeZnOkCpCc3lONTXn+0i9SSSGIs uNGJ1ddcmLRD7K/5IqUZg7H2d0K7g3NWCEhv7+aZzrp9gGBfkRAoHhIE6NvYQYV5okUP dD396Fe0R2PyrilKPorTyAmmbH3K1YJgQSRPeaCRysaqQqpu97xRT5ZcXUmF5dUTBtev 2F6u3q5+iF/Nib/GoR0svxvt+D7rKajHRB8pZpeF53k9VftQJfsTGli/eLk3ju40MLlv AaaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version; bh=8KWDjgxjkK14YtOseeoefF0cPU6Gh0NcS5voa78XMZw=; fh=m79KtjqDAQ1WN2aHOXsnEscAa1F2FAXhGNIlhI4DXQM=; b=FD3Saw8pgJEF6zUv+lfvZfDrUeQmjycj8xbo+VsyzzeJl9d5OJbKWUVTFL9erwdgcn UwUJtlz+cfwUJQAHCAACByxTySUTdmp+znm4h2RGMRtJ51RPAlxNxK7ALE9CgleUUkt9 HShwkZMpflymbBEVX0Ia6epD/zWvKWl2GMCGRKmuTi0dNkY0+JLNIbkNAZNhyD9LWxQN 8+RRoP5hQYrIssIyHCBy0aXPJMV0CjBYfVa9K7sIvl3CQH+AwZj1TAewJ4Ji2aQbcOju lBQIxt6QoVYZKbQ+nlxOgVq0c7AgaNwsFKGJETpHEpofo9mgUvQTecRm2JN/tSyapIpD AsEQ==; darn=freebsd.org ARC-Authentication-Results: i=1; mx.google.com; arc=none X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1781196862; x=1781801662; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8KWDjgxjkK14YtOseeoefF0cPU6Gh0NcS5voa78XMZw=; b=R7O3xRncoB9wF7cBtG1rWQn+JoJRzGF/4Bp4tfoQuJ/xsQUol8WVYhH0j36JtqG/M3 UQEzCl79XVtRwwg5xPUcJfKD0hyxokow4NN1ao3pDfCEnn+JqG7gthkKDh3CCQNkU3l9 BzUxP+djE73Xn7gYKYzYe6RnhTK1XuiM3uX/hsxME1bJKkWcilXPCLqAe9XQpa0jzWLT XSEhV2uMrNYIe/RkGfZsodyvSbPbk+Wxezvw3IoTmqZKta5c9dZHuBUFfUHvsFKgnhKZ 3sfoCQZlbYsOk57h+xhVOvff1mKZdR0BrGKHu6xpijiRJ6EJlbltRab8aYs1ijhN+AdV y1HA== X-Gm-Message-State: AOJu0YzKLfoT2Jze3E33dPGPBUt+nMIFRuGvxv5ztcy0TLIJr71SUpsO 4I5RhRXjtpiZGvsVIrmue6/mq0TNkANzuscD6kqL92Im6L3Ubn4950WfjOmUNliZc7IVnXx7mJ2 EeLvq4ETRzfWA/G8Gm9eU7iSwb3JDKlQ= X-Gm-Gg: Acq92OEoabuh1hYGHXhDEx21q1MqHicwXBWfTYWBVIfDc6tbIABe3qO8+70MnpbrQZY MaZDUcqylGpQbejl1k8TKURO9AOgR87iHAuWYITA6jin7KGEwn1SBL0/n2a1dD4Zv0Gvu3bqX5K RSitBD51729bANw8mUUsIMz2Y3QF4NDKY4/QRHSSGpCQzDQ8OI1svZd5EFQihWPs/Pz49TmUkEc Zc7zISi8nt1TyQoyiQqbz2bq9nRv09a83XV40fM++A4ykJTA7jym3F8irahbXBUb8VJ1c7U/r2P jxCctU5xEHI3CGqRIzVsJ0wVZ8Gw8Cp5oAZKfPIY4CVLnRAH84nx7Rrs8u3OVJuMcu4pk4UIxI4 7Fi9eKq+4iTRoFVxokFWd1/Mw700= X-Received: by 2002:a05:620a:31aa:b0:915:8076:9e77 with SMTP id af79cd13be357-9160ad40d37mr574016785a.42.1781196861523; Thu, 11 Jun 2026 09:54:21 -0700 (PDT) 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 References: In-Reply-To: From: Adrian Chadd Date: Thu, 11 Jun 2026 09:54:09 -0700 X-Gm-Features: AVVi8Cel8saQ6IFCn15dpsb0kYqKBuwTq8hqZZLD7RXBkQhyaTmqYfRFbhqAF5I Message-ID: Subject: Re: Proposal to switch powerpc64le to IEEE-754 binary128 To: Piotr Kubaj Cc: freebsd-ppc@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4gbpdp5338z4182 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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, which 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 reinstallation > won't be necessary, upgrade is just the usual buildworld + installworld. > > * 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 -HEAD (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 Rust, > 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 with > them that also uses long double type will misbehave. I'm also currently > playing with ldc and it will also need to be updated. Ok, can you go investigate GCC and LLVM too? And go, maybe? Does go currently work on ppc64le? > > * 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 not > 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. -adrian