benchmalarkey
When small changes in an ajacent piece of code result in reproducable and statistically significant changes to the outcome of a synthetic benchmark, even thought the benchmark does not evaluate the part of the code which has changed.
Looks like benchmalarkey, better try enabling -mbranches-within-32B-boundaries.