Since there are many variants of architectures, some are supported and others could be supported in the future, it becomes a little annoying for end-users to browse the configurable options and enable specific options to get maximum speed for corresponding algorithms so here --enable-fat comes in handy. I like the idea of making --enable-fat default to get over the case that the user didn't notice it or unaware of its advantages and disadvantages and therefore hesitant to choose it, so I think it's a good time to enable fat option by default if things are stable in assembly side, you got my vote.
regards, Mamone On Sat, Dec 26, 2020 at 6:13 PM Niels Möller <ni...@lysator.liu.se> wrote: > ni...@lysator.liu.se (Niels Möller) writes: > > > 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. > > I've pushed a couple of changes to increase version numbers, and add to > the NEWS file. > > One question: Is this a good time to make --enable-fat the default? It's > been available for a couple of versions, I think using it is quite > common, and I've not heard about any problems (except build failures if > assembler doesn't recognize newish instructions, which at least isn't > subtle). > > Regards, > /Niels > > -- > Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. > Internet email is subject to wholesale government surveillance. > _______________________________________________ > nettle-bugs mailing list > nettle-bugs@lists.lysator.liu.se > http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs > _______________________________________________ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
