-
Notifications
You must be signed in to change notification settings - Fork 5k
JIT: Do not report duplicate EH clauses to VM #114895
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
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
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. Thank you!
c6cb6a4
to
07c0a5a
Compare
src/coreclr/tools/aot/ILCompiler.Reflection.ReadyToRun/EHInfo.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Filip Navara <filip.navara@gmail.com>
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.
I think you should update the JIT-EE GUID
Also, update docs/design/coreclr/botr/clr-abi.md |
It looks like SOS in https://github.com/dotnet/diagnostics knows about dumping duplicated clauses. What is the compat story there? Does it need to run against older runtimes, or is it tightly bound to a runtime version? Does this limit changing corhdr.h/corinfo.h? @mikem8361 |
Will do.
I removed the section for "duplicated clauses". There's another out-of-date section for "cloned finallys". Not sure how to reword it since it talks about JIT32, JIT64 and desktop CLR. |
Keeping it as draft until we resolve the question about dotnet/diagnostics and updates to clr-abi.md. |
Per the discussion in previous PR, it should be fine to delete everything that is not relevant to current main. |
The code would continue to work but stop reporting the duplicate clauses and cloned finallys when running with newer runtime/DAC. I think that's fine since the runtime doesn't use the information so the value of reporting it is dubious at best. It's still useful for older runtimes. I'd be happy to hear a second opinion though. |
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
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.
Thank you!
A filter ACD may change region number because some other EH region was deleted. Handle this properly. Fixes dotnet#114895
A filter ACD may change region number because some other EH region was deleted. Handle this properly. Fixes dotnet#114895
A filter ACD may change region number because some other EH region was deleted. Handle this properly. Fixes dotnet#114895
A filter ACD may change region number because some other EH region was deleted. Handle this properly. Fixes #114895
Fixes #114891