-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
#73662 introduces a strict weak ordering violation in a comparator #108618
Labels
Comments
Can you please provide a backtrace? |
Sure, here it is:
|
tmsri
pushed a commit
to tmsri/llvm-project
that referenced
this issue
Sep 19, 2024
The sort used the block name as a tie-breaker, which will not work for unnamed blocks and can result in a strict weak ordering violation. Fix this by checking that all exiting blocks dominate the latch first, which means that we have a total dominance order. This makes the code structure here align with what optimizeLoopExits() does. Fixes llvm#108618.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#73662 / d77067d introduces an assertion failure when Clang is compiled with the strict weak ordering check for comparators enabled in libc++ check (
-D_LIBCPP_DEBUG_STRICT_WEAK_ORDERING_CHECK
):The text was updated successfully, but these errors were encountered: