|
From: John W. <jw...@st...> - 2004-07-30 10:24:30
|
I've checked in a fix to the satcount() bug, and added a regression test to check for it. I was wondering what I should check in next. I have two more items in the patch I sent around: 1. Automatic generation of BDD trace files. This is controlled by a compile-time switch, so if you don't define the switch, nothing is changed. Basically it involves adding a line at the start of every BDD API function, and changing "return" instructions to a "RETURN" macro. It touches almost every function in BuDDy, but I think it is pretty minor because it will be disabled by default. 2. Preallocation of memory for node table. Without this patch, BuDDy runs out of memory very quickly, especially on Windows machines (at as low as 12M nodes). This patch reduces the fragmentation by preallocating a large memory area and performing initialization on demand. This is about a 10 line patch. I sent the proposed patches to the mailing list earlier. Does anyone have any thoughts/ideas/concerns about these changes? Another alternative is that I can check them in under a new CVS branch until people are convinced of the stability. -John |