Edit - Retrocomputing Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2

Getting exactly-known execution time on modern x86 (to avoid timing jitter as @Brian H commented) could means burning a lot of those very short clock cycles checking an accurate timesource to make the normal case run at the same speed as the worst case for cache misses, branch mispredicts, or whatever. e.g. this rdtsc deadline spin loop (under a non-Linux OS, or on an isolated core).
– Peter Cordes
Commented Oct 17, 2020 at 14:41

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »