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

Test failure: JIT\\Regression\\JitBlue\\GitHub_35821\\GitHub_35821\\GitHub_35821.cmd #36206

Closed
v-haren opened this issue May 11, 2020 · 5 comments · Fixed by #38855
Closed

Test failure: JIT\\Regression\\JitBlue\\GitHub_35821\\GitHub_35821\\GitHub_35821.cmd #36206

v-haren opened this issue May 11, 2020 · 5 comments · Fixed by #38855
Assignees
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI JitStress CLR JIT issues involving JIT internal stress modes
Milestone

Comments

@v-haren
Copy link

v-haren commented May 11, 2020

failed in job: runtime-coreclr jitstress-isas-arm 20200509.1

Error message

Assert failure(PID 19192 [0x00004af8], Thread: 18764 [0x494c]): Assertion failed 'varTypeIsFloating(tree->TypeGet())' in 'projs.GitHub_35821:Main(System.String[]):int' during 'Assertion prop' (IL size 48)

 File: F:\workspace\_work\1\s\src\coreclr\src\jit\assertionprop.cpp Line: 2434
 Image: C:\h\w\AF270949\p\CoreRun.exe


Return code: 1
Raw output file: C:\h\w\AF270949\w\A48408EF\e\JIT\Regression\Reports\JIT.Regression\JitBlue\GitHub_35821\GitHub_35821\GitHub_35821.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\AF270949\p\corerun.exe" GitHub_35821.dll 
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=C:\h\w\AF270949\p
> C:\h\w\AF270949\w\A48408EF\e\JIT\Regression\JitBlue\GitHub_35821\GitHub_35821\GitHub_35821.cmd
Expected: True
Actual: False


Stack trace
   at JIT_Regression._JitBlue_GitHub_35821_GitHub_35821_GitHub_35821_._JitBlue_GitHub_35821_GitHub_35821_GitHub_35821_cmd() in F:\workspace\_work\1\s\artifacts\tests\coreclr\Windows_NT.arm64.Checked\TestWrappers\JIT.Regression\JIT.Regression.XUnitWrapper.cs:line 124106
@v-haren v-haren added the JitStress CLR JIT issues involving JIT internal stress modes label May 11, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI untriaged New issue has not been triaged by the area owner labels May 11, 2020
@BruceForstall BruceForstall added this to the 5.0 milestone May 11, 2020
@BruceForstall BruceForstall removed the untriaged New issue has not been triaged by the area owner label May 11, 2020
@BruceForstall
Copy link
Member

From CoreCLR Windows_NT arm64 Checked jitstress_isas_nohwintrinsic_nosimd,

set COMPlus_TieredCompilation=0
set COMPlus_EnableHWIntrinsic=0
set COMPlus_FeatureSIMD=0

@echesakovMSFT @kunalspathak @tannergooding @CarolEidt

@kunalspathak
Copy link
Member

I will take a look. This is the new test that I added last week.

@kunalspathak
Copy link
Member

I believe this is an existing issue that got exposed because of this test case. The C# version of the test is simple. We just need to create Vector64.Create(double_imm) and pass it to method.

Test3(Vector64.Create(23.1));
		
[MethodImpl(MethodImplOptions.NoInlining)]
public static void Test3(Vector64<double> data) {}

This repros only if COMPlus_FeatureSIMD=0. With that, we inline Vector64.Create(double value) implementation which is Unsafe.As() as seen here. Then we try to constant propagate the value of double in assertion prop. But when we try to do it same for the tree node that represents the result, we hit assert here because tree->TypeGet() == TYP_SIMD8. I think the right fix would be to not do constant propagation in such case. I didn't see an easy way to repro it for other types like TYP_SIMD16, etc. because we might not inline the implementation of Vector128.Create(double).

@briansull , @BruceForstall - can one of you confirm my understanding?
@tannergooding - I assume that even you would hit this in your #36267.

@CarolEidt
Copy link
Contributor

I believe that the fundamental problem here is the retyping that we do of TYP_SIMD8 return types as TYP_DOUBLE. I believe that the right answer here is to never retype TYP_SIMD return values as TYP_DOUBLE, just as we're moving away from retyping other struct return types. I think @sandreenko might also want to comment here.

@sandreenko sandreenko self-assigned this May 13, 2020
@sandreenko
Copy link
Contributor

The issue should be resolved with JitDoOldStructRetyping = false, I will check that once I finish support for arm32.

Thanks for the analysis.

sandreenko pushed a commit to sandreenko/runtime that referenced this issue Jul 7, 2020
Closes dotnet#36206, closes dotnet#36418.

The issue was fixed by dotnet#37499.
sandreenko pushed a commit that referenced this issue Jul 8, 2020
* Reenable GitHub_26491.

Closes #13355

* Reenable crossgen2 tests failing with old retyping/

They were fixed both with and without retyping.
Closes #37883.

* Reenable HVA merge cases.

Closes #37341, closes #37880.

* Reenable GitHub_35821.

Closes #36206, closes #36418.

The issue was fixed by #37499.

* Delete extra lines that are no longer needed.

#37506 was fixed in #38241.

* delete a throwing init.
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI JitStress CLR JIT issues involving JIT internal stress modes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants