-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Arm64/Sve: Implement the SVE APIs that takes 32-bit address as input #103297
Labels
Milestone
Comments
kunalspathak
added
Priority:3
Work that is nice to have
arm-sve
Work related to arm64 SVE/SVE2 support
labels
Jun 11, 2024
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Jun 11, 2024
dotnet-policy-service
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jun 11, 2024
@dotnet/arm64-contrib |
vcsjones
added
area-System.Runtime.Intrinsics
and removed
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
labels
Jun 12, 2024
Tagging subscribers to this area: @dotnet/area-system-runtime-intrinsics |
@kunalspathak Is the 9.0.0 milestone appropriate for this, or should we set it to 10.0.0? |
jeffhandley
removed
the
untriaged
New issue has not been triaged by the area owner
label
Jul 20, 2024
kunalspathak
added a commit
to kunalspathak/runtime
that referenced
this issue
Sep 12, 2024
kunalspathak
added a commit
that referenced
this issue
Sep 13, 2024
* Remove entry of APIs because of #103297 * comment out the test cases for unsupported APIs
kunalspathak
added a commit
to kunalspathak/runtime
that referenced
this issue
Sep 13, 2024
) * Remove entry of APIs because of dotnet#103297 * comment out the test cases for unsupported APIs
kunalspathak
added a commit
to kunalspathak/runtime
that referenced
this issue
Sep 13, 2024
) * Remove entry of APIs because of dotnet#103297 * comment out the test cases for unsupported APIs
jeffschwMSFT
added a commit
that referenced
this issue
Sep 13, 2024
jtschuster
pushed a commit
to jtschuster/runtime
that referenced
this issue
Sep 17, 2024
) * Remove entry of APIs because of dotnet#103297 * comment out the test cases for unsupported APIs
sirntar
pushed a commit
to sirntar/runtime
that referenced
this issue
Sep 30, 2024
) * Remove entry of APIs because of dotnet#103297 * comment out the test cases for unsupported APIs
mikelle-rogers
pushed a commit
to mikelle-rogers/runtime
that referenced
this issue
Dec 10, 2024
) * Remove entry of APIs because of dotnet#103297 * comment out the test cases for unsupported APIs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are several APIs that operates on truncated address such that it is valid in 4GB memory range. We implemented the APIs, but realized that adding test might not be straight forward because it will involve calling
VirtualAlloc
or equivalent to make sure that the address is in that range. As such we decided to skip such APIs and add them opportunistically if time permits.Related discussion: #103159 (comment)
The text was updated successfully, but these errors were encountered: