-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[KnownBits] Remove hasConflict()
assertions
#94568
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
Changes from all commits
87a6753
98b3368
5878f24
3726812
10b0837
7cfe894
4e550dc
5896305
afd2123
3faba75
1f7034c
4c9696a
7f965e2
6f48b46
cfe2878
f44acee
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4212,7 +4212,6 @@ KnownBits SelectionDAG::computeKnownBits(SDValue Op, const APInt &DemandedElts, | |
break; | ||
} | ||
|
||
assert(!Known.hasConflict() && "Bits known to be one AND zero?"); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe just focus on the middle-end initially and then look at removing the DAG/GlobalISel assertions later? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I feel like it's safer to get rid of it everyone at once. |
||
return Known; | ||
} | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.