5 ms·
Automatic SIMD Vectorization for Haskell [pdf]
- zvrba 13y agoAnd a link NOT pointing to scribd: http://www.leafpetersen.com/leaf/publications/icfp2013/vectorization-haskell.pdf http://www.leafpetersen.com/leaf/publications/icfp2013/vecto...
- dbaupp 13y agoThe submission link points to that, the `[scribd]` is a separate mirror added automatically by HN.
- seanmcdirmid 13y agoYa, its always tough to figure that out. Design fail.
- miga 13y agoThey also changed the title of the post. It was: "Intel Labs Haskell Compiler: Automated..."
- sfvisser 13y agoI still think it's truly awesome that I can just hapilly write my code in Haskell on a very high level, while in the meantime other people will hack on the compiler and core libraries and magically make my programs run faster! Seriously, thank you for doing research in this area. It will put us forward.
- DanWaterworth 13y agoHaskell is all about the lazy.
- Avshalom 13y agoYou can apparently blame C for the belief that a programmer should have to optimize code themselves. Though I'm waiting for the itanium/ILP optimized haskell compiler. It's one of the few languages that tracks side effects enough that it seems possible to actually build the "sufficiently smart compiler" that Intel always claimed would materialize to make itanium a good idea.
- taeric 13y agoWhat would you blame them for? Beating the crap out of the alternatives?
- dons 13y ago"Intel Labs Haskell Research Compiler" ... !!!
- ginko 13y agoSo it's going to be throttled on AMD CPUs?
- DanWaterworth 13y agoWhy? My impression is that it isn't used outside of intel.
- simcop2387 13y agohttp://en.wikipedia.org/wiki/Intel_C%2B%2B_Compiler#Criticism http://en.wikipedia.org/wiki/Intel_C%2B%2B_Compiler#Criticis... It's a reference to that incident where intel's C compiler was checking the vendor strings to turn on certain optimized pathways.
- mjn 13y agoRelevant to the discussion about targeting LLVM vs. C in another thread (https://news.ycombinator.com/item?id=6096965 https://news.ycombinator.com/item?id=6096965), Section 2 says they compile via C, but through an intermediate language, Pillar, that adds support for second-class continuations, precise garbage collection, and a few other things. Here's an older paper on Pillar: http://www.leafpetersen.com/leaf/publications/lcpc2007/pillar-lcpc.pdf http://www.leafpetersen.com/leaf/publications/lcpc2007/pilla...
- bombita 13y agoWhy do always the best link on HN on high performance, non-trivial compilers or parallelism get little to no comments?
- kps 13y agoIt did get voted to the front page, so there is interest, but very few readers are able to add anything useful.
- saucetenuto 13y agoPeople write comments when they feel that they have useful contributions to make. It is much easier to notice that you have nothing worthwhile to say about a vectorizing compiler than about, say, the NSA. One way to get around this is to go meta, e.g. to discuss the commenting habits of others instead of the submission.
- bombita 13y agoI went meta myself, sorry about that.
- saucetenuto 13y agoNo apology needed, I was trying to make fun of myself, not you.