This repository has been archived by the owner on Jul 1, 2022. It is now read-only.
ASM fix: checking support ADX instructions is now done in assembly #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ction wrapper that generate memallocs upstream
… not met but F.NoCarry is.
… by a previous goff version
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using function pointers to chose in
init()which version to call (assembly or not, depending on available instruction set) trigger some unwanted memory allocation in caller libraries.FromInterface()(package wide) now follows convention of other setters and isz.SetInterface(..)MulAssign,AddAssignandSubAssignAPIs are marked as deprecated and just wrap theMul,AddandSub.