3 ms·
Windows NT was intended to be multi-arch. NT 3.1 (the initial release) ran on x86, mips, and alpha; in 1993, Alpha (and generally, RISC) was clearly the future.
by toast0 4y ago
Windows NT was intended to be multi-arch. NT 3.1 (the initial release) ran on x86, mips, and alpha; in 1993, Alpha (and generally, RISC) was clearly the future. NT 3.5 and 4.0 added PPC, also clearly the future. Windows 2000 included Alpha support up through at least Release Candidate 1. Although public builds were all 32-bit only. Having a working 64-bit system to build a 64-bit OS on is pretty useful though, because during the time of windows 2000, 64-bit was clearly the future. The Alpha architecture's very weak memory model is also super helpful as a test platform, because you have to put the right memory fences in or stuff won't work. Going from x86 to Alpha is hard, because all your insufficient fences hit all at once, going from Alpha to x86 is easy, because you've found all the missing fences already.
- xxpor 4y agoSome call the Alpha memory model useful, some call it completely fucking insane. Dependent loads can be reordered! The mental overhead of working in that paradigm is just not worth it.
- toast0 4y agoI'm not saying it's good for the overall system. Your choice on that. I'm just saying it's a useful memory model for making sure all your memory fences are in place. If you can run your OS/application there, it's hard to find a place it won't run. That said, Alphas were mighty fast during their prime, I don't know if that was enabled by the insane memory model or just coincidence?
- aidenn0 4y ago> That said, Alphas were mighty fast during their prime, I don't know if that was enabled by the insane memory model or just coincidence? There were many of the same people working on: - First 3 generations of DEC Alpha - StrongARM - SiByte MIPS (later purchased and rebranded by Broadcom) - PASemi POWER - PASemi was then aqui-hired by Apple for making ARM chips These don't have any particularly unifying memory model, but were all quite performant, so while this may be a different coincidence, I suspect that the people involved are more likely a contributing factor to the performance than the memory model.
- meepmorp 4y agoDon't forget forget AMD
- xxpor 4y ago>I'm just saying it's a useful memory model for making sure all your memory fences are in place. Oh for sure. It's just that it's like saying a nuclear bunker will be fine if you drop a pound of dynamite on it :) >I don't know if that was enabled by the insane memory model I have to imagine it was, especially since back then the "optimization" parts of CPUs weren't nearly as advanced as they are today (branch predictors, OOO execution that still maintains the memory model guarantees, etc). Alphas were dead before my time, but I have to imagine the tradeoff was a) their expense, and b) the time it actually took to write software and track down concurrency bugs due to everything being talked about here.
- zdw 4y agoSecurity folks depend on this for correctness checks - OpenBSD in particular continues to supports Alpha (memory access reordering, alignment requirements) and Sparc64 (big endian, register windows), as well as the usual suspects, which frequently finds bugs that wouldn't be found on platforms without those "unusual" characteristics.
- xxpor 4y agoSpecifically on memory ordering bugs though, philosophically speaking, are they actually bugs if the condition is impossible to hit on a given platform? From an OpenBSD perspective, I can see it being valuable to know that it means the code can be safely ported to any random arch that comes out in the future, but for more commercial software, I really can't see that being worth the time worrying about.
- nyanpasu64 4y agoI think compilers are free to reorder code at compile time assuming single-threaded execution, exposing the same bugs that memory ordering exposes at runtime. I'm not sure if MSVC does this or not.
- xxpor 4y agoThere are a lot of details, but essentially yes. To solve that, see the compiler barriers section in https://www.kernel.org/doc/Documentation/memory-barriers.txt https://www.kernel.org/doc/Documentation/memory-barriers.txt