David Terei wrote: > Can you fork GHC on github and put your > patch up on there and then send me a link please? This is just a far > easier workflow for me to review and merge patches than email.
Sure, will do. > Hmmm I wasn't expecting a huge speedup but was hoping for a few > percentage points at least. With 20/20 hindsight I'm not that surprised. The NCG backend path looks like: CMM -> native asm -> native assembler -> object code while the LLVM backend path looks like: CMM -> llvm code -> llc -> native asm -> native assembler -> object code The thing thats different here is that GHC generates LLVM text IR code that then has to be parsed by llc. I wonder if it might be worth print LLVM btyecode instead of LLVM text IR code. Although it would probably be better to instrument things first and find out whats really happening. It would also be useful to check out the nofib tests that are the slowest to try and figure out why. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/ _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
