Skip to content
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

Vector128.IsHardwareAccelerated always returns false in debugger #69576

Closed
danmoseley opened this issue May 19, 2022 · 3 comments
Closed

Vector128.IsHardwareAccelerated always returns false in debugger #69576

danmoseley opened this issue May 19, 2022 · 3 comments

Comments

@danmoseley
Copy link
Member

I'm using Visual Studio 17.2 using 7.0.100-preview.5.22267.11 SDK targeting 7.0.100-preview.5.22267.11 runtime.

using System.Runtime.Intrinsics;

Console.WriteLine(Vector128.IsHardwareAccelerated);

This writes true for me, but Vector128.IsHardwareAccelerated in the watch window (or hovering) is always true. this doesn't happen for eg., Sse2.IsSupported.

@tannergooding

@ghost ghost added the untriaged New issue has not been triaged by the area owner label May 19, 2022
@ghost
Copy link

ghost commented May 19, 2022

Tagging subscribers to this area: @dotnet/area-system-runtime-intrinsics
See info in area-owners.md if you want to be subscribed.

Issue Details

I'm using Visual Studio 17.2 using 7.0.100-preview.5.22267.11 SDK targeting 7.0.100-preview.5.22267.11 runtime.

using System.Runtime.Intrinsics;

Console.WriteLine(Vector128.IsHardwareAccelerated);

This writes true for me, but Vector128.IsHardwareAccelerated in the watch window (or hovering) is always true. this doesn't happen for eg., Sse2.IsSupported.

@tannergooding

Author: danmoseley
Assignees: -
Labels:

area-System.Runtime.Intrinsics

Milestone: -

@tannergooding
Copy link
Member

This is a simple fix. These aren't recursive where-as Sse.IsSupported and friends are.

I'll have a fix up shortly, just need to add a test validating things.

@tannergooding tannergooding self-assigned this May 19, 2022
@tannergooding tannergooding added bug and removed untriaged New issue has not been triaged by the area owner labels May 19, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label May 19, 2022
@tannergooding
Copy link
Member

Closing this as a duplicate of the older #38162

@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jun 4, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants