Re: i386 baseline issue for Go packages in Bookworm
On 4/17/21 7:09 PM, Shengjing Zhu wrote:
> Hi,
>
> As the release of Go 1.16, upstream no longer supports x87-only floating-point.
>
> https://golang.org/doc/go1.16#386
>
>> require at least SSE2 support on 386, raising Go's minimum GOARCH=386
>> requirement to the Intel Pentium 4 (released in 2000) or
>> AMD Opteron/Athlon 64 (released in 2003).
>
> So we have 3 options for Go packages on i386 in Bookwarm.
>
> 1. Raise the i386 baseline to SSE2.
> 2. Downgrade the Go packages to softfloat.
> 3. Build all Go packages with GCCGO on i386.
>
> As for the option 3, I don't how best is supported by upstream.
> But most packages may work, if some specific packages FTBFS after switching
> to GCCGO, they need to be removed on i386 unfortunately.
>
> What people prefer for the 3 options?
1: I'd like to avoid that. package tests, symbols files, anything else is
written for x87. It's a change which comes with a lot of extra work from my
point of view.
2: No opinion.
3: I didn't check golang vs. gccgo. It seems to work for some packages. Expect
some version skew, e.g. bullseye has golang 1.15.x, and gccgo 1.14.x.
Extrapolating bookworm that will be golang 1.19.x and gccgo 1.18.x.
Matthias
Reply to: