4 ms·
For better or worse I have a very big soft spot for things in programming that go fast, even moreso for things that go really fast. I look forward to learning
by FridgeSeal 9y ago
For better or worse I have a very big soft spot for things in programming that go fast, even moreso for things that go really fast.
I look forward to learning more Rust so I can get an excuse to use this.
- dboreham 9y agoBack in the day we had to add extra STOP statements at the end of our Fortran programs if the machine was really fast because it would crash through the first one or two.
- FridgeSeal 9y agoReally? That's actually awesome! CPU's and GPU's are capable of breakneck speeds, so I love to see things that really make the most out of the capacity available.
- dboreham 9y agoNope. This is what used to pass for a programmer joke. STOP C Add a couple more stop statements in case someone runs this on a Cray and it is going so fast it breaks though the first one: STOP STOP
- Someone 9y agoWell, there is this: http://elixir.free-electrons.com/linux/latest/source/arch/x86/kernel/process.c#L360 http://elixir.free-electrons.com/linux/latest/source/arch/x8... Yes, Linux does the equivalent of while(true) { halt } I don’t think that code will loop, but why take the risk? There is/was a detailed description of what it takes to stop an OS that included multiple ways to stop the CPUs, executed in order in the hope/expectation that one of them would work that in the end hit a similar loop, but I can’t find it anymore.
- chime 9y agoThere used to be a Turbo button on most PCs in the 90s which would be on by default but could be disabled to support games made for slower CPUs.
- k__ 9y agohehe, yes! When I was young I never understood why someone would turn turbo mode off.