Originally Posted by alexh
Can / have you code profiled it to see where most of the CPU time is taken up?
I think Storm C++ V4 had a profiler with their hacked gcc v2.9? I'm using a newer version of gcc 3.4, don't know of any working profiler that I can use
Don't even have a working debugger, makes any kind of Amiga development very difficult (I've learnt to write lots of logging statements).