#compiler-optimization

#compiler-optimization

But there's a problem with this sort of trick: how do you know the compiler will keep doing it? What happens when the compiler's next release comes out? How can you catch performance regressions? One solution is benchmarking: you measure your code's speed, and if it gets a lot slower, something has gone wrong. This is useful and important if you care about speed. But it's also less localized, so it won't necessarily immediately pinpoint where the regression happened.