-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Assertion failed 'i < BitSetTraits::GetSize(env)' #111344
Labels
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
in-pr
There is an active PR which will close this issue when it is merged
Known Build Error
Use this to report build issues in the .NET Helix tab
Milestone
Comments
EgorBo
added
the
Known Build Error
Use this to report build issues in the .NET Helix tab
label
Jan 13, 2025
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Jan 13, 2025
dotnet-policy-service
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jan 13, 2025
EgorBo
added
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
and removed
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
labels
Jan 13, 2025
Probably one of my changes |
Here the loop backedge is a catch return
The lexical last block is BB14 and that's where we put the slow path preheader, but it's in the middle of a handler region that we need to clone, and this confuses the cloning code. |
AndyAyersMS
added a commit
to AndyAyersMS/runtime
that referenced
this issue
Jan 14, 2025
In some unusual cases the last block of a loop might be in the middle of a handler region (say the loop backedge is in a catch, and the catch has alternate flow that exits the loop). Make sure that we properly place the slow loop preheader into the same EH regions as the fast loop preheader. Fixes dotnet#111344
dotnet-policy-service
bot
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jan 14, 2025
JulieLeeMSFT
removed
the
untriaged
New issue has not been triaged by the area owner
label
Jan 14, 2025
AndyAyersMS
added a commit
that referenced
this issue
Jan 15, 2025
) In some unusual cases the last block of a loop might be in the middle of a handler region (say the loop backedge is in a catch, and the catch has alternate flow that exits the loop). Make sure that we properly place the slow loop preheader into the same EH regions as the fast loop preheader. Fixes #111344
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
in-pr
There is an active PR which will close this issue when it is merged
Known Build Error
Use this to report build issues in the .NET Helix tab
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=914793&view=ms.vss-test-web.build-test-results-tab&runId=24152400&resultId=215618&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
Build error leg or test failing:
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=914793
Error message validated:
[Assertion failed 'i < BitSetTraits::GetSize(env)'
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 1/13/2025 9:38:44 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: