3 ms·
Fair point. At this point, it's a very leaky abstraction because not all levels of "random access" (e.g. L1 cache vs. main memory) are created equal.
by michaelochurch 14y ago
Fair point. At this point, it's a very leaky abstraction because not all levels of "random access" (e.g. L1 cache vs. main memory) are created equal.
- w3pm 14y agoTrue, and this is my biggest problem with writing optimized code in C -- it takes a lot of guessing and inspecting the generated assembler and understanding your particular platform to make sure you're ACTUALLY utilizing registers and cache like you intend. If there were some way of expressing this intent through the language and have the compiler enforce it, that'd be fantastic :) That said, there's really not a better solution to the problem than C, just pointing out that even C is often far less than ideal in this arena.
- stmartin 14y agoWhat kind of a masochist are you, sir?
- carterschonwald 14y agoi'm actually spending much of my time these days having a go writing HPC codes in haskell. So far, the generated assembly looks pretty darn awesome, and the performance pretty competitive with alternatives i have access too :)