Your message dated Fri, 10 Jul 2020 07:52:15 +0800
with message-id
<CAKcpw6USGhdwJxjayH9tKwi8xVnfAN6JAkuf7dUt4+OC=qf...@mail.gmail.com>
and subject line Re: Bug#949259: buster-pu: package linux/4.19.67-2+deb10u1
has caused the Debian Bug report #949259,
regarding buster-pu: package linux/4.19.97-1 MIPS ABI preparation for bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
949259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian....@packages.debian.org
Usertags: pu
In Jessie and Buster cycles, we finished the process from FP32 to FPXX.
And I test the whole Buster archive, and be sure that all packages are
built with FPXX now.
Since FPXX uses only even FPRs, then wastes other 16 FPRs.
And another problem of FPXX is that it may need help of RAM for some operation.
FP64 also has better co-operation with MIPS SIMD Architecture (MSA).
The CONFIG_MIPS_O32_FP64_SUPPORT has just enabled in master branch of
kernel-team/linux[2].
Is it possible to enable this config for buster? So we can start the
migration to FP64 now,
and release it with bullseye.
Otherwise we will have to start this work after bullseye released.
[1]. https://web.archive.org/web/20180828210612/https://dmz-
portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking
https://salsa.debian.org/kernel-team/linux/merge_requests/199
--- End Message ---
--- Begin Message ---
Adam D. Barratt <a...@adam-barratt.org.uk> 于2020年7月10日周五 上午3:58写道：
>
> On Sun, 2020-02-16 at 16:27 +0000, Ben Hutchings wrote:
> > This was discussed on IRC with Julien Cristau, but unfortunately I
> > didn't save a log. The main points that came up were:
> >
> > * Executables built for the O32 FP64 ABI require this kernel config
> > change and older kernel versions will refuse to load them. So the
> > kernel needs to be upgraded before installing any binaries built
> > for the new FP ABI.
> >
> > * Normally the support for an additional ABI would be included in
> > release N.0 and used in N+1. Since this was not present in 10.0,
> > it
> > would be possible for users to start upgrading to bullseye while
> > still running a kernel that does not support O32 FP64. We need to
> > prevent them getting a broken system.
> >
> > * Julien proposed that libc6 would have a preinst check on the kernel
> > when it is changed to use the new FP ABI. Presumably all binaries
> > built for the new FP ABI should also have a versioned dependency on
> > at least this version of libc6.
> >
> > So I don't see any reason not to update the kernel configuration
> > already, as it will remain compatible with the O32 FPXX binaries in
> > buster. Only the user-space changes in unstable (libc6 and
> > toolchain) need to be carefully coordinated.
>
> As far as I can see, this was enabled in 4.19.118-1, but is about to be
> reverted due to causing issues. Is that accurate? If so, should we
> close this request now?
Yes. It is closed now.
>
> Regards,
>
> Adam
>
--- End Message ---
