-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Add AVX-512 testing pipeline #77930
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
Add AVX-512 testing pipeline #77930
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsIntroduce DOTNET_JitForceEVEXEncoding to force EVEX encoding when possible. This will fail when not an an AVX-512 capable machine, by design (to know we are properly testing on capable machines). Current pipeline definition only runs coreclr tests with JitForceEVEXEncoding set. Currently defined to automatically trigger when one of the JIT files instrsxarch.h, emitxarch.cpp, or emitxarch.h are changed, as it is expected these will be changed frequently as the AVX-512 feature is implemented. It is also expected this will be manually triggered as appropriate. Eventually, this pipeline will be removed and tests folded into the existing jitstress-isas-x86 pipeline.
|
cc @dotnet/jit-contrib |
Introduce DOTNET_JitForceEVEXEncoding to force EVEX encoding when possible. This will fail when not an an AVX-512 capable machine, by design (to know we are properly testing on capable machines). Current pipeline definition only runs coreclr tests with JitForceEVEXEncoding set. Currently defined to automatically trigger when one of the JIT files instrsxarch.h, emitxarch.cpp, or emitxarch.h are changed, as it is expected these will be changed frequently as the AVX-512 feature is implemented. It is also expected this will be manually triggered as appropriate. Eventually, this pipeline will be removed and tests folded into the existing jitstress-isas-x86 pipeline.
2b2c6fe
to
13adcab
Compare
Those OSes currently do not have AVX-512 capable machines in our test lab.
@tannergooding @kunalspathak @dotnet/jit-contrib PTAL |
Latest test run triggered: https://dev.azure.com/dnceng-public/public/_build/results?buildId=75649&view=results |
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.
LGTM
Introduce DOTNET_JitForceEVEXEncoding to force EVEX encoding when possible. This will fail when not an an AVX-512 capable machine, by design (to know we are properly testing on capable machines).
Current pipeline definition only runs coreclr tests with JitForceEVEXEncoding set. Currently defined to automatically trigger when one of the JIT files instrsxarch.h, emitxarch.cpp, or emitxarch.h are changed, as it is expected these will be changed frequently as the AVX-512 feature is implemented. It is also expected this will be manually triggered as appropriate. Eventually, this pipeline will be removed and tests folded into the existing jitstress-isas-x86 pipeline.