[Arm64] Support table-driven code generation for scalar intrinsics #447
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
… between table-driven and special intrinsics in jit/hwintrinsiccodegenarm64.cpp
Dotnet-GitSync-Bot
added
the
area-CodeGen-coreclr
|
@dotnet/jit-contrib Can someone please review this? This PR is a copy of #208. I had to re-open it since my fork was created before the runtime repo went public and I couldn't push anymore changes. |
CarolEidt
approved these changes
Dec 2, 2019
ghost
locked as resolved and limited conversation to collaborators
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.
Motivation 1: To support table-driven approach during code generation of "simple" scalar intrinsics (the ones that don't require non-trivial instruction lookup or moving the values between operand registers and destination register).
Motivation 2: To support special (non table-driven) codegen of intrinsics with 3 operands (e.g.
BitwiseSelect).When I implemented these logics for scalar intrinsics and 3 operands intrinsics I found that functions
CodeGen::genHWIntrinsicandCodeGen::genSpecialIntrinsichave at least 50% of the identical code so I moved the shared preparatory logic (that looks up intrinsic ID and category, the corresponding operand nodes, and base type) to a separate classHWIntrinsic.This way I could remove special codegen for
NI_ArmBase_LeadingZeroCountNI_ArmBase_Arm64_LeadingSignCountNI_ArmBase_Arm64_LeadingZeroCount.