Test failure baseservices\\exceptions\\unittests\\RecursiveThrowNew\\RecursiveThrowNew.cmd #75944
Assignees
Labels
arch-arm64
arch-x64
arch-x86
area-CodeGen-coreclr
CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
blocking-clean-ci-optional
Blocking optional rolling runs
JitStress
CLR JIT issues involving JIT internal stress modes
os-linux
Linux OS (any supported distro)
os-mac-os-x
macOS aka OSX
os-windows
Milestone
Comments
dotnet-issue-labeler
bot
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsRun: runtime-coreclr jitstress 20220919.1 Failed test: Error message:
|
v-wenyuxu
added
arch-arm64
os-linux
|
One more assert in rationalize. Assigning to @BruceForstall. @jakobbotsch PTAL. |
|
Looks related to #75842, apparently the threading added there was not enough (or perhaps incorrect). I'll look into a fix tomorrow. |
|
Wonder if the failures we now see in #62689 are also related. |
|
Seems like it is from changes made in |
AndyAyersMS
added a commit
to AndyAyersMS/runtime
that referenced
this issue
Sep 21, 2022
Under jit stress, `optOptimizeBoolsGcStress` will modify trees. Since this now happens in a phase that runs after `fgSetBlockOrder`, it must also recost and rethread the trees. Fixes dotnet#75944.
ghost
added
the
in-pr
|
This is not a 7.0 issue. |
ghost
removed
the
in-pr
AndyAyersMS
added a commit
to AndyAyersMS/runtime
that referenced
this issue
Sep 27, 2022
In some cases the value of a block's branch predicate is correlated with the predecessor of the block. Often this correlation is hinted at by the presence of phis in the predicate's tree and/or phi VNs in in the predicate's VN graph. For each predecessor of a block, we evaluate the predicate value number using the values brought to the block by that predecessor. If we find correlations, we use them to drive the existing jump threading optimization. Also, if we end up partially disambiguating such that there is just one remaining predecessor, update the value number of the predicate to reflect the values that flow in from that predecessor. Fixes dotnet#75944. Contributes to dotnet#48115.
AndyAyersMS
added a commit
that referenced
this issue
Sep 29, 2022
In some cases the value of a block's branch predicate is correlated with the predecessor of the block. Often this correlation is hinted at by the presence of phis in the predicate's tree and/or phi VNs in in the predicate's VN graph. For each predecessor of a block, we evaluate the predicate value number using the values brought to the block by that predecessor. If we find correlations, we use them to drive the existing jump threading optimization. Make sure that when we search local PHIs we also match the ssa def number to ensure we're looking at the right PHI. Also, if we end up partially disambiguating such that there is just one remaining predecessor, update the value number of the predicate to reflect the values that flow in from that predecessor. Fixes #75944. Contributes to #48115.
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run: runtime-coreclr jitstress 20220919.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: