-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
benchmark -C codegen-units=N #39
Comments
I don't know what's "beefier" but I gave it an attempt with my i7-5930K @ 4.3 GHz. This is what
In short, it looks like a wash to me too. I also ran the comparison with the AVX options:
The differences are bigger but it still feels like noise to me. |
Thank you! That confirms my suspicion – there's either just not enough code to make a difference or thinLTO removes what difference is left. |
Apparently, the default changed to
codegen-units=16
. However, when benchmarking I don't see a clear winner between N=1 or N=16 – it shows some small win on byte counting and some small loss onnum_chars
, but in both cases, it's a wash. Perhaps someone else can benchmark on a beefier machine?The text was updated successfully, but these errors were encountered: