-
Notifications
You must be signed in to change notification settings - Fork 262
Add RISC-V scalar fallback support #318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
carlos (carlosqwqqwq)
wants to merge
2
commits into
microsoft:main
Choose a base branch
from
carlosqwqqwq:riscv-directxmath
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need to update the library instead of just defining
-D_XM_NO_INTRINSICS_in your build?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right that defining
_XM_NO_INTRINSICS_is sufficient, so this change is not required to make a RISC-V consumer build.The narrower rationale for handling
__riscvin the header is to give a recognized target a consistent default. DirectXMath is header-only and is often included transitively, so otherwise every consumer build must know about and propagate a DirectXMath-specific macro to every translation unit. Selecting the existing scalar implementation avoids that integration requirement; it does not claim RISC-V intrinsics, RVV optimization, or comprehensive platform validation.I have narrowed the PR accordingly: it now contains only the target-selection change and a short documentation note. I removed the CMake message and the RISC-V-specific changes to the x86 extension headers.
If the project's policy is that scalar-only targets should explicitly opt in with
_XM_NO_INTRINSICS_, then the build define is the appropriate solution and the library change is not strictly necessary.