Page MenuHomePhabricator

[analyzer] Drop explicit mention of range constraint solver
ClosedPublic

Authored by ddcc on Nov 15 2016, 1:11 PM.

Details

Summary

The basic constraint solver was dropped in rL162384, leaving the range constraint solver as the default and only constraint solver. Explicitly specifying it is unnecessary, and makes it difficult to test with other solver backends.

Diff Detail

Repository
rL LLVM

Event Timeline

ddcc updated this revision to Diff 78060.Nov 15 2016, 1:11 PM
ddcc retitled this revision from to [analyzer] Drop explicit mention of range constraint solver.
ddcc updated this object.
ddcc added reviewers: zaks.anna, dcoughlin.
ddcc added a subscriber: cfe-commits.
zaks.anna accepted this revision.Nov 30 2016, 10:42 PM
zaks.anna edited edge metadata.

Awesome!!! Thanks for the cleanup!

This revision is now accepted and ready to land.Nov 30 2016, 10:42 PM
zaks.anna edited edge metadata.Nov 30 2016, 10:42 PM
zaks.anna added a subscriber: NoQ.
NoQ added a comment.Nov 30 2016, 10:46 PM

Approve! And probably -analyzer-store=region is worth dropping as well eventually.

This revision was automatically updated to reflect the committed changes.