Algorithms/go-perfbook
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

improve examples working around poor code generation with complicated code

Browse Source
This commit is contained in:
Damian Gryski 2018-11-25 07:57:35 -08:00
parent 639e13fb8f
commit ff9d71d367
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
performance.md
View File

@ -612,7 +612,13 @@ especially when upgrading Go versions that your code doesn't become "worse".
There are definitely cases where tweaks to work around the lack of a particular
compiler optimization became slower once the compiler was improved.
TODO: https://github.com/golang/go/commit/9eb219480e8de08d380ee052b7bff293856955f8)
My RC6 cipher implementation had a 10% speed up for the inner loop just by
switching to `encoding/binary` and `math/bits` instead of my hand-rolled
version.
Similarly, the `compress/bzip2` package was sped by by switching to [simpler
code the compiler was better able to
optimize](https://github.com/golang/go/commit/9eb219480e8de08d380ee052b7bff293856955f8)
If you are working around a specific runtime or compiler code generation
issue, always document your change with a link to the upstream issue. This