at the moment, tc/CO4/Test/TermComp2014/Main.hs repeatedly removes at least one rule, each time using the same configuration. This is wasting time. There should be a driver program that applies some cheap methods first.
semantic labelling (with increasing bit width etc.)
And of course, if an expensive step was successful, then start again with the cheap ones, starting with re-computing the EDG (it may look different since we removed some rules). This is the "recursive decomposition" method from http://www.jaist.ac.jp/~hirokawa/publications/03cade.pdf (Sect. 4)
at the moment, tc/CO4/Test/TermComp2014/Main.hs repeatedly removes at least one rule, each time using the same configuration. This is wasting time. There should be a driver program that applies some cheap methods first.
Cheap methods are (without sem. labeling)
Then more expensive methods from the co4 tree
And of course, if an expensive step was successful, then start again with the cheap ones, starting with re-computing the EDG (it may look different since we removed some rules). This is the "recursive decomposition" method from http://www.jaist.ac.jp/~hirokawa/publications/03cade.pdf (Sect. 4)
The strategy of the main program should be expressed by something like https://github.com/jwaldmann/transformer-combinators but the API looks somewhat ugly.