On Tue, Dec 15, 2020 at 10:47 AM Niels Möller wrote:
>
> Hi, I wonder if it would make sense to try to cut a release pretty soon
> (and without any arm64 changes)? Previous release was made end of April,
> and there's been quite a few improvements since then.
It would be nice if cpu feature
Hi Niels and Maamoun,
On Fri, Dec 18, 2020 at 07:18:24PM +0200, Maamoun TK wrote:
> > One problem with the current state is that big-endian arm is most likely
> > broken. I don't want to delay the release for that though, since I'm not
> > able to fix it. If anyone is able to test and fix, soon
>
> I think the powerpc64 code is in good shape now, and ready for release. Are
> you aware of anything that needs fixing?
>
No, all what I can think of are a couple of issues that make the powerpc64
code more stable (you can check their merge requests in the repo).
> One problem with the
Maamoun TK writes:
> It seems gcc for aarch64 doesn't support building 32-bit binaries, maybe we
> should remove the check of ABI since 64-bit is the only option.
Ok, that's a bit confusing. There's a command line flag for it, not -m32
but -mabi=ilp32, but that doesn't work out of the box with
Andreas Metzler writes:
> it would not count as transition
> https://release.debian.org/bullseye/freeze_policy.html#transition
Thanks, good to know.
> cu And- I am not hinting that delaying a release until after the
> start of the transition freeze would be welcome ;-)-reas
Right, if
I created a couple of merge requests in the repo, with those MRs merged I
think the powerpc code is stable to be included in the upcoming version of
nettle.
regards,
Mamone
On Thu, Dec 17, 2020 at 12:28 PM Maamoun TK
wrote:
> I wonder which assembly files we should use if target host is
