-
Notifications
You must be signed in to change notification settings - Fork 0
M5: Correctness #14
Copy link
Copy link
Open
Labels
area/correctnessAlive2, lit, FileCheck, llvm-reduce, fuzzingAlive2, lit, FileCheck, llvm-reduce, fuzzingkind/milestoneTracking issue for a whole milestoneTracking issue for a whole milestonepriority/p1Needed this milestoneNeeded this milestone
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area/correctnessAlive2, lit, FileCheck, llvm-reduce, fuzzingAlive2, lit, FileCheck, llvm-reduce, fuzzingkind/milestoneTracking issue for a whole milestoneTracking issue for a whole milestonepriority/p1Needed this milestoneNeeded this milestone
Four weeks. Part V, correctness. This sits before the backend rather than at the end on purpose. Once you have watched a solver hand you a counterexample you stop trusting your own reasoning about poison, and that is the right state of mind for everything after it.
Exit criterion. V06's treatment of boundedness is reviewed and confirmed not to oversell, because every Alive2 claim in the project links there.
Tasks
irx.reduceandirx.litReduceTraceandAliveVerdictwidgetsGates
update_test_checks.pyintegration produces tests an LLVM reviewer would accept, confirmed by asking oneThe V06 gate is a quality bar item as much as a content one. Alive2 unrolls loops to a fixed depth, so "no counterexample found" is strong evidence and is not a proof, and a reader who leaves this project believing otherwise has been taught something false by the one lesson that was supposed to prevent that.