Extend EliminateRedundantTryFinally
in ReduceNestingTransform
#2959
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to issue(s) this covers:
N/A
Problem
When decompiling
EventPipeMetadataGenerator.GenerateMetadata(int eventId, string eventName, long keywords, uint level, uint version, EventOpcode opcode, EventParameterInfo[] parameters)
fromSystem.Private.CoreLib
from .NET 7.0.4 the decompiler does not completely clean up try finally regions left over from the pinned region decompilation step.Before change:
After change:
The code responsible for removing this redundant try-finally was extended to account for a potential additional
leave
ILAst instruction present in the single block of the try container.I did not add any unit tests as I was unable to get the compiler to produce an assembly which triggered this bug. In case the assembly I am working with is necessary for easier analysis I have provided it in a zip archive below.
System.Private.CoreLib.zip