I got cset++/2 about a week ago, in case you're interested.  

The following results are not necessarily representative, and were done
with a program with heaps of "inline"s, and the optimizer would
have spent years trying to optimize it, when they weren't really speed
critical anyway.  It's worth getting cset++/2, just to watch the compiler
have to do some hard work.  The funny thing is though, that a lot of the
optimization time was spent on disk access, no idea why.

25 seconds to compile non-optimized with cset++/2
run time 59 seconds
60k executable

8 minutes 25 seconds for optimized with cset++/2
run time 38 seconds
120k executable

9 seconds to compile xword6 optimized with BC++
run time 41 seconds
30k executable

Paul

---