Re:GHC 7 is released. with LLVM, improved inliner, improved ...
by batterseapower on Thursday March 03, 2011 @04:08PM
(#2285788)
Yes, the title is confusing. GHC 7.02 is significant because it will be included in the next Haskell Platform release -- GHC 7.01 was only available separately, and was not much installed.
GHC 7.01 was also a time of upheaval in the code base, with an almost total rewrite of the type checker. This was a bit buggy at first, but early experience with 7.01 means that it is much more polished in 7.02.
Re:GHC 7 is released. with LLVM, improved inliner, improved ...
by JoachimSchipper on Friday March 04, 2011 @04:48AM
(#2287577)
Yes, but that's usually in the second digit (e.g. 2.4 is stable, 2.5 is development) - switching from unstable to stable in a nominal patch release (third digit) is at least uncommon.
GHC 7.01 was also a time of upheaval in the code base, with an almost total rewrite of the type checker. This was a bit buggy at first, but early experience with 7.01 means that it is much more polished in 7.02.
The full changelist from 7.0.1 is modest and available at http://www.haskell.org/ghc/docs/7.0.2/html/users_guide/relea...
http://www.haskell.org/ghc/docs/7.0.1/html/users_guide/relea...
Previously on HN:
http://news.ycombinator.com/item?id=1908503
* K sparks scheduled over * M lightweight threads scheduled onto * N OS threads over * C hardware cores.
The runtime manages this, and does load balancing.
I'm pretty sure they use a M:N language-thread to OS-thread system. So they need to decide what thread to put "on" an OS-thread at any given time.