https://github.com/tokenrove/dispatch-comparison
Do not use: rhetorical benchmark
https://github.com/tokenrove/dispatch-comparison
bad-code benchmark wip x86-64
Last synced: 9 months ago
JSON representation
Do not use: rhetorical benchmark
- Host: GitHub
- URL: https://github.com/tokenrove/dispatch-comparison
- Owner: tokenrove
- Created: 2016-07-22T02:13:42.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2017-10-03T15:11:34.000Z (about 8 years ago)
- Last Synced: 2025-02-14T07:25:50.975Z (11 months ago)
- Topics: bad-code, benchmark, wip, x86-64
- Language: Python
- Homepage: http://www.cipht.net/2017/10/03/are-jump-tables-always-fastest.html
- Size: 8.79 KB
- Stars: 4
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
*Do not use this code!*
This is some benchmarking code I wrote several years ago and came back
to a few times, in support of [a blog post I finally published]. One
of the reasons I delayed finishing that post so long was that I
realized *the methodology used here is flawed*. It's enough for us to
make a (weak) point, but shouldn't be taken seriously.
I'll do something like this again soon, and hopefully that will set a
better example.
There is both a Makefile that will do things, and a Python program
(`run-experiment.py`) that will do similar things. The Makefile is
broken but convenient. Many of the options for programs here don't
actually do anything.
You have been warned.
[a blog post I finally published]: http://www.cipht.net/2017/10/03/are-jump-tables-always-fastest.html