-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Performance regression since 7.0.0 on godbolt #2153
Comments
I wasn't repro this locally and compiling with |
Hi there! How might I check? |
I thought you might have a library build log. {fmt} cmake script prints the build type, e.g.:
|
It's all good, this is working as intended: we only build debug in Compiler Explorer as it stands. CC @partouf . CE is not really designed for performance testing, so it's not bee a problem. And one can't easily see the results of linking against a static library either. We can look in to it if it's a problem |
Good to know, thanks for investigating! This is not a problem, just a bit surprising. Is there any particular reason debug build is the default? |
Debug is the default as it gives the best library attribution (according to @partouf "mostly to not mix, but it also helps when inlining the libraries with being able to identify the library code") |
@vitaut @mattgodbolt Thanks a lot to check it (unf. last night I've had only a browser to do...) |
Thanks @BuzaL . This is a kick for us to consider options in Compiler Explorer. |
Comparing to 6.2.1 version, most of the format (expect FMT_COMPILE) getting about 4-5 times slower, regardless of C++ version and compiler:
https://godbolt.org/z/TGn1cx
The text was updated successfully, but these errors were encountered: