> Just to clarify: if we build yi the library with profiling, and yi the > executable without profiling - would we still hit that major slowdown?
Correct. Building yi the library with profiling, as you probably know, results in two libraries: A profiling library and a non-profiling library. Building the executable without profiling only links the executable with the non-profiling libraries. Which do not experience the slowdown. > (And on a side-note, is that a GHC bug? I had thought profiling an > executable, when you weren't using it, cost you a few % but wasn't > supposed to cost you a whole lot.) That's what I thought too. :-\ I've been attempting to break down the test to check if this is a compiler regression. If it is then it's clearly a bug. If not it could still be a bug but then the issue will just be harder to track down. Cheers, Corey O'Connor --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
