| ▲ | Gibbon1 an hour ago | |
Processors I mostly write firmware for have little cache at all. I think cache friendly code also tends to be reason about friendly and debugger friendly. None of that is remotely premature optimization. | ||
| ▲ | dataflow an hour ago | parent [-] | |
> I think cache friendly code also tends to be reason about friendly and debugger friendly. Not sure what examples you have in mind, but the very first things I think of when I hear cache friendly code are cache-blocking and cache-oblivious algorithms, which are quite the opposite of that. See also B-trees vs. binary search trees, etc. | ||