Details
- Reviewers
dblaikie - Commits
- rG1b25fce404d4: [OpaquePtr] Make cmpxchg work with opaque pointers
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/IR/Verifier.cpp | ||
---|---|---|
3854–3856 | Is there missing testing for this? Looks like the wording/assert was changed, but no test cases were updated for this? |
llvm/lib/IR/Verifier.cpp | ||
---|---|---|
3854–3856 | I think we could ever reasonably reach these since the bitcode reader and llparser will both already give up if this were to fail. And there's a similar assert when actually creating the instructions. |
llvm/lib/IR/Verifier.cpp | ||
---|---|---|
3854–3856 | Yeah, if they're unreachable I'd be inclined to remove them. The only thing that comes to mind would be in a non-asserts build, using a unit test/API testing - build it then verify. But that's testing behavior that's out-of-contract (behavior behind a failed assertion) anyway, which isn't reasonable in my opinion. So, yeah, if you can't get there in a +Asserts build via API, bitcode, or textual IR, I'd say it's dead code & be fine with dropping it (probably do that in a separate preliminary commit, though) |
llvm/lib/IR/Verifier.cpp | ||
---|---|---|
3854–3856 | sounds good, I'll delete these in a future change |
Is there missing testing for this? Looks like the wording/assert was changed, but no test cases were updated for this?