02.10.2013, 13:43, "Paulo Matos" <[email protected]>: > Hi, > > I am curious as to why things like this happen: > running 16 interestingness tests in parallel > ===< pass_blank :: 0 >=== > (0.0 %, 458340 bytes) > ===< pass_lines :: 0 >=== > (-1.2 %, 463811 bytes) > > Shouldn't size increase be dismissed?
Some creduce passes deliberately increase code size to provide better input for further passes. This is not exactly true for pass_lines - it should decrease file size on each step, however, first step is special as it runs topformflat, which may increase file size. So, if you see size increasing only at the first step after ===< pass_lines :: N >===, it's OK. > Then I see repeatedly: > (-1.2 %, 463811 bytes) > (-1.2 %, 463805 bytes) > (-1.2 %, 463801 bytes) > (-1.2 %, 463789 bytes) > > I am using a version that's about a year old. Maybe it's time to upgrade > which brings me to two other questions: > * Creduce has quite a few dependencies, making it quite an annoying process > to install on my machine at work. Are there any 64bit static binaries out > there? > * Is the latest Creduce compatible with LLVM 3.3 stable? Yes, but newer revision of clang/llvm will run faster. -- Regards, Konstantin
