Keith Wansbrough <[EMAIL PROTECTED]> writes: > So while Hugs gives you a reduction count (or even a millisecond > duration), this is essentially meaningless: in a real application > you would compile the code with an optimising compiler. The effect > this can have on your execution time can easily be more than merely > a constant factor: it can change the order of your algorithm. Is this true in practice? That is, are there programs which have different asymptotic running times when compiled under ghc or hbc than when running under Hugs? It would actually surprise me if there were; I'm having a hard time imagining a realistic optimization that would do this. (Which could easily be a failure of my imagination.) Carl Witty [EMAIL PROTECTED]
- RE: Reduction count as efficiency measure? Hans Aberg
- Re: Reduction count as efficiency measure? Lennart Augustsson
- Re: Reduction count as efficiency measure? Jan Skibinski
- RE: Reduction count as efficiency measure? Hans Aberg
- RE: Reduction count as efficiency measure? Jan Skibinski
- Re: Reduction count as efficiency measure? Fergus Henderson
- Re: Reduction count as efficiency measure? Lennart Augustsson
- Re: Reduction count as efficiency measure? Graeme Moss
- Re: Reduction count as efficiency measure? Graeme Moss
- Re: Reduction count as efficiency measure? Keith Wansbrough
- Re: Reduction count as efficiency measure? Carl R. Witty
- Re: Reduction count as efficiency measure? Amr A Sabry
- Re: Reduction count as efficiency measure? Ralf Hinze
- Re: Reduction count as efficiency measure? Carl R. Witty
- Re: Reduction count as efficiency measure? Lennart Augustsson
- RE: Reduction count as efficiency measure? Simon Peyton-Jones
- Re: Reduction count as efficiency measure? Bart Demoen
- Re: Reduction count as efficiency measure? Olaf Chitil