-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
JIT: Add FlowEdge destination block member #98243
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsPart of #93020. Per conversation in #98054, I'm going to try to replace
|
Diff results for #98243Throughput diffsThroughput diffs for windows/arm64 ran on windows/x64MinOpts (-0.00% to +0.01%)
Details here Throughput diffs for linux/arm ran on windows/x86Overall (+0.00% to +0.01%)
FullOpts (+0.01%)
Throughput diffs for windows/x86 ran on windows/x86Overall (+0.00% to +0.01%)
FullOpts (+0.00% to +0.01%)
Details here |
cc @dotnet/jit-contrib, @AndyAyersMS PTAL. This is a somewhat vain attempt to split up the successor edge work into smaller changes. I anticipate the next PR -- replacing the successor block pointers with successor edge pointers in |
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.
Note we will get the memory back (and then some) when we remove the min and max edge weights.
Part of #93020. Per conversation in #98054, I'm going to try to replace
BasicBlock
's block successor pointers (bbTarget
,bbFalseTarget
, etc) withFlowEdge
pointers to simplify access to successor edges. To do this, each edge is going to need access to its destination block, so that access to successor blocks is still simple. As a first step, add a destination block member toFlowEdge
.