3 ms·
Did you miss the part about where the bug was found using the current versions of GCC to build the current versions of OCaml? It's lazy to the point of dishone
by acdha 9y ago
Did you miss the part about where the bug was found using the current versions of GCC to build the current versions of OCaml?
It's lazy to the point of dishonesty to act as if Microsoft is the only one with decades of accumulated code.
- jstimpfle 9y agoThere is still a point that proprietary binaries are probably the biggest force keeping decades of cruft in processors. (Not judging here)
- etatoby 9y agoPrecisely. I would go as far as saying proprietary binaries for Microsoft systems are the single force making Intel processors keep decades of cruft, considering the immense cost that Intel must bear to keep those old instructions (barely) running on modern processors.
- striking 9y agoThose "decades of cruft" are usually emulated in microcode and not actual silicon. Intel knows very few people use the BCD instructions, but it costs them almost nothing to keep them in while running them slightly slower than most operations. Why mess up a stable API when you don't have to?
- deleted 9y ago[deleted]