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

Baseline more pri1 tests with native AOT #111068

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

MichalStrehovsky
Copy link
Member

I originally thought this found a real bug but this is just a really weird test exercising not just slow delegate creation path, but also quite invalid IL:

IL_0124: newobj instance void FakePower::.ctor()
IL_0129: stloc.s V_4
IL_012b: ldloc.0
IL_012c: dup
IL_012d:
ldvirtftn instance int32 FakePower::Power4(int32,int32)
IL_0133: newobj instance void OddPower/MyDeleg2::.ctor(object,
native int)

(Notice that despite the newobj, the actual object instance is of a completely different type and the method is not on that type, took a while to realize the newobj is useless and unrelated.)

Cc @dotnet/ilc-contrib

I originally thought this found a real bug but this is just a really weird test exercising not just slow delegate creation path, but also quite invalid IL:

https://github.com/dotnet/runtime/blob/3d88f276b13ae4d2ffa6a66b02f32171fdc825b5/src/tests/JIT/Methodical/delegate/_simpleoddpower.il#L510-L517

(Notice that despite the newobj, the actual object instance is of a completely different type and the method is not on that type.)
Copy link
Contributor

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

@jkotas
Copy link
Member

jkotas commented Jan 3, 2025

really weird test exercising not just slow delegate creation path, but also quite invalid IL

Should we delete this test instead?

@MichalStrehovsky
Copy link
Member Author

really weird test exercising not just slow delegate creation path, but also quite invalid IL

Should we delete this test instead?

@dotnet/jit-contrib for opinion on the deletion since it's a JIT test.

@MichalStrehovsky
Copy link
Member Author

@dotnet/jit-contrib for opinion on the deletion since it's a JIT test.

@dotnet/jit-contrib any opinion about deleting the test? If no opinion, I would prefer committing as-is (only disable on native AOT).

@MichalStrehovsky
Copy link
Member Author

@dotnet/ilc-contrib could someone have a look at this test disablement?

@amanasifkhalid
Copy link
Member

@dotnet/jit-contrib any opinion about deleting the test? If no opinion, I would prefer committing as-is (only disable on native AOT).

Sorry for the lack of response on our end -- I don't think we have an opinion on this.

@MichalStrehovsky
Copy link
Member Author

@dotnet/jit-contrib any opinion about deleting the test? If no opinion, I would prefer committing as-is (only disable on native AOT).

Sorry for the lack of response on our end -- I don't think we have an opinion on this.

Thanks, assumed that. It is invalid IL, but there's probably some reason for it. I don't mind if native AOT doesn't have matching behavior for invalid IL so I'm fine just disabling it, just need someone to agree and sign off.

@MichalStrehovsky MichalStrehovsky merged commit 0530b55 into dotnet:main Jan 30, 2025
68 of 70 checks passed
@MichalStrehovsky
Copy link
Member Author

Thank you!

@MichalStrehovsky MichalStrehovsky deleted the pri1more branch January 30, 2025 22:29
grendello added a commit to grendello/runtime that referenced this pull request Jan 31, 2025
* main:
  JIT: fix case where implied subrange assertions can get lost in morph (dotnet#112020)
  Propose new async API (dotnet#110420)
  Move the diagnostic print for stack overflow test failure (dotnet#112001)
  JIT: Fold more nullchecks (dotnet#111985)
  Baseline more pri1 tests (dotnet#111068)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants