|
|
|
|
|
by dist1ll
1312 days ago
|
|
> C is fast because it's close to how CPU and memory actually work. Out-of-order execution, cache hierarchies, branch prediction, virtual memory, pipelining, vector instructions, ILP, NUMA are all pretty transparent to the C spec. Trying to accommodat hardware quirks with C feels like blackbox engineering. It's certainly better than with managed languages but still.... |
|
I don't know of any other way of manipulating the cpu as closely as C and assembly. Do you?