2009/2/16 Scott L. Burson <Scott@...>:
> On Sun, Feb 15, 2009 at 1:31 PM, Richard M Kreuter <kreuter@...>
>> If you're convinced that you like your code as it is but
>> are unhappy with the compiler's intermittent resource usage, you might
>> try toggling CP off before compiling the offending method.
>> * (setq sb-c::*constraint-propagate* nil)
> Maybe this could be made a little more accessible by having a SPEED of 0 or
> 1 turn off CP?
Something like that would be nice, yes, but unfortunately not trivial:
That is, correct transformations used by the compiler can cause bogus
type mismatch warnings if constraint propagation is skipped. There are
also other optimization phases which it might be good to skip, but
which currently cannot be, as other parts of the compiler assume they
are always run.
So, possible, but going to take some work and thought.