| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch null
|
Sorry, something went wrong.
|
The failures above are for the release-mode debug info testing. With cross-block we remove the store at IL offset 0 and this causes the validation to fail. Going to just add another exemption here... I'm surprised something downstream doesn't catch this already (basically x + 0 => x), but without an immediate zero. |
Sorry, something went wrong.
|
Looks like a bug has crept in, possibly from the JTRUE assertions. |
Sorry, something went wrong.
|
/azp run runtime-jit-experimental, runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr outerloop |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 4 pipeline(s). |
Sorry, something went wrong.
|
jit-experimental failure was that the fgEntryBB was getting emtpy-merged, in cases where other flow optimizations more or less remove all the other blocks save one, and so fgBBcount was off by one going into morph. This currently can only happen with OSR stress. |
Sorry, something went wrong.
|
FYI @dotnet/jit-contrib Latest diffs. Main impact here is a code size improvement; TP results are mixed but "average" out to about zero. |
Sorry, something went wrong.
|
/azp run Fuzzlyn |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, very nice to see this enabled. I kicked off a Fuzzlyn run with it enabled.
Sorry, something went wrong.
|
I have perf lab data too but so far it's indistinguishable from noise; I almost suspect the feature is not getting enabled, |
Sorry, something went wrong.
|
The Fuzzlyn runs will hit #95318 so we'll probably have to do a bit digging to see if there is anything else. |
Sorry, something went wrong.
I only see the unexpected small type asserts. |
Sorry, something went wrong.
The number of examples found does not match up with the number of those assertion occurrences... But I'm not totally sure whether those counts are accurate or not given the number of examples found. |
Sorry, something went wrong.
|
#95249 was merged now so I'm going to rerun Fuzzlyn to be sure. |
Sorry, something went wrong.
|
/azp run Fuzzlyn |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
|
Do those runs merge up or do we need a new merge from main? |
Sorry, something went wrong.
All good. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Collated set of improvements (lower is better) as of 12-12-23. 134 benchmarks improved.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Enable cross-block assertion prop by default.