what im seeing from this chart is that we should be using the nop instruction for everything
Well the best code is no code. Nop could be second best though.
Assembly Hall of Shame
11–20 of 104 posts
Re: Assembly Hall of Shame
#12Oh wow, glad to see Chris Domas active online again!
Re: Assembly Hall of Shame
#13It’s crazy how computers still seem to get perceivably slow every few years, given how many instructions can be executed in 1ms. Shameful, even.. What’s that law called about programmers wasting all the compute on abstraction?
Huh? A millisecond is an eternity!
I remember reading once somewhere:
If some app responds in 10ms or less, it is INTERACTIVE.
makes you think.
Re: Assembly Hall of Shame
#14Nop should be #1, because it is infinitely slow for what it does. ;)
Re: Assembly Hall of Shame
#15Related, and linked in the readme: https://github.com/xoreaxeaxeax/smiiiiiiiiiiiiiiii (using the slow instructions to break SMI)
Re: Assembly Hall of Shame
#16Nop should be #1, because it is infinitely slow for what it does. ;)
It increments rip by one.
Re: Assembly Hall of Shame
#17Very cool! Also, huh interesting. I’ve used rdtsc to measure cycle diffs but had no idea its execution takes that long. Is that common across architectures?
Re: Assembly Hall of Shame
#18It’s crazy how computers still seem to get perceivably slow every few years, given how many instructions can be executed in 1ms. Shameful, even.. What’s that law called about programmers wasting all the compute on abstraction?
Wirth's Law I believe.
Re: Assembly Hall of Shame
#19It’s crazy how computers still seem to get perceivably slow every few years, given how many instructions can be executed in 1ms. Shameful, even.. What’s that law called about programmers wasting all the compute on abstraction?
The OS should do less not more