A few AVX tests failing when XSAVE is disabled at OS level

[VSadov]

While working on #47212 , I did some testing with XSAVE disabled. (as in bcdedit /set xsavedisable 1)

One thing that I noticed is that a few clr tests failed, without any of my changes.
Most likely it is an issue with feature detection in the test harness. Everything else works fine and Libs tests were all passing.

Logging this just in case this is something unexpected or worth fixing.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[VSadov]

CC: @tannergooding

Tagging subscribers to this area: @tannergooding
See info in area-owners.md if you want to be subscribed.

Issue Details

---

While working on #47212 , I did some testing with XSAVE disabled. (as in bcdedit /set xsavedisable 1)

One thing that I noticed is that a few clr tests failed, without any of my changes.
Most likely it is an issue with feature detection in the test harness. Everything else works fine and Libs tests were all passing.

Logging this just in case this is something unexpected or worth fixing.

Author:	VSadov
Assignees:	-
Labels:	area-System.Runtime.Intrinsics, untriaged
Milestone:	-

[tannergooding]

I'll take a look tomorrow. Do you happen to know which of the tests were failing?

CC. @jeffhandley

[VSadov]

@tannergooding I did not catch what tests failed exactly. I saw a few AVs in the output and it was all about vector types.

Knowing that I have disabled XSAVE, I am pretty sure it is AVX related. Also knowing that everything works fine otherwise, which means regular feature detection is ok, it must be something with the tests or harness.

It is probably not a high priority if it is test-only. Hard to see someone getting into this by accident.

[VSadov]

This is a very old issue and also a test-only corner case. I think at this point we are sure that it is ok as-is.