-
Ah yes. The speedup-loop.
https://thedailywtf.com/articles/The-Speedup-Loop-
This is brilliant.
-
-
I think some compilers will just drop that in the optimization step.
-
Real pain in the ass when you're in embedded and your carefully placed NOPs get stripped
-
asm("nop");
-
-
Homer: "oh yeah speed
holessleep"-
Sleep holes
-
-
-
Tell the CPU to wait for you?
Na, keep the CPU busy with useless crap till you need it.
-
Fuck those other processes. I want to hear that fan.
-
I paid good money for my fan, I want to know it's working!
-
-
Have you considered a career in middle management
-
-
On microcontrollers that might be a valid approach.
-
I've written these cycle-perfect sleep loops before.
It gets really complicated if you want to account for time spent in interrupt handlers.
-
Thankfully I didn't need high precision realtime. I just needed to wait a few seconds for serial comm.
-
-
-
This should be the new isEven()/isOdd(). Calculate the speed of the CPU and use that to determine how long it might take to achieve a 'sleep' of a required time.
-
I took an embedded hardware class where specifically we were required to manually calculate our sleeps or use interrupts and timers rather than using a library function to do it for us.
-
-
Its a thing. https://en.m.wikipedia.org/wiki/Busy_waiting
-
Javascript enters chat:
await new Promise(r => setTimeout(r, 2000));Which is somehow even worse.
-
As someone who likes to use the CPU, I don't think it's worse.
-
I mean, it’s certainly better than pre-2015.
-
-
I actually remember the teacher having us do this in high school. I tried it again a few years later and it didn't really work anymore.
-
I can relate. We have breaks ate work too.
-
You gotta measure the latency of the first loop.
-
I just measured it, and this takes 0.17 seconds. And it's really reliable, I added another zero to that number and it was 1.7 seconds
-
Sudo sleep
