search for: comparesf

...r llvm-test as an example. You can do make TEST=llc to generate custom reports. If this change can somehow be optionally controlled, then you can set it as llcbeta option and write a custom report that compare the time spend in some particular passes (TEST.beta-compare is an example, but it comparesf number instructions). The biggest problem is right now time spent in scheduling is lumped into "DAG->DAG Instruction Selection" time because it's part of the pass. It would be nice if we can somehow bring it out. Evan > > -Da...

On Saturday 22 December 2007 02:33, Evan Cheng wrote: > > After some very simple testing, I see slowdowns of around 1.7%. I > > assume > > this is ok, but want to check. > > Can you clarify? Is this 1.7% slowdown of scheduling time or overall > codegen time? If it's the later, then it seems a bit too much. Also, > please test it with all the

...as an example. > You can do make TEST=llc to generate custom reports. If this change > can somehow be optionally controlled, then you can set it as llcbeta > option and write a custom report that compare the time spend in some > particular passes (TEST.beta-compare is an example, but it comparesf > number instructions). I'll look at this. But it would be nice to get this change (or something similar) in ASAP. The scheduler is just broken right now. So either we have a compiler with a slight slowdown in some cases or we have a compiler that exhibits undefined behavior. > The b...