acuozzo
Joined 15 years ago
Joined 15 years ago
No, you're not. You've promoted yourself into middle management. Congratulations.
Explain how this would not lead to an eventual Eloi & Morlocks situation.
Finding out how to make the best use of the large amount of DDR3 RAM I have.
Those Chinese C612-based boards for the E5-2696v3, et al. (which support DDR3 and DDR4) seem OK with the custom BIOSen out there.
It could be that my affinity for port & madeira biases me, but the wine-haters I know have all expressed a strong dislike of what they described as its "acidity".
Lots and lots of information is not online. You'd be surprised.
It makes large allocations fail which would have otherwise succeeded.
"When you need it" is a state you can only enter into, AFAICT, when you approach the limit gradually, not abruptly.
I'm also not upset. I just want to know which compilers you're using which honor the "register" keyword in C.
Clang targeting LLVM, despite the name, produces binaries compiled 100% ahead-of-time.
The "LLVM" is just the intermediate representation used by the compiler. GCC uses GIMPLE and RTL.
> In C... it is still possible to bake what is placed in "register" a priori
By what mechanism? Even ancient GCC circa 1989 ignored the "register" keyword/storage-class. Automatic register allocation algorithms have been the default for a long time. You have to go back to the K&R days to find a compiler willing to honor it (or find an esoteric compiler like AZTEC C for the 6502).