You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observed on macOS Mojave x86-64 with Clang 11.0.0, and OpenBSD/macppc 6.8 with Clang 10.0.1.
scummtr is approximately 30% faster with GCC than with Clang, when importing a translation.
GCC 10.2.0 and GCC 4.2.1 at -O2 are both faster than Clang at -O2 or -O3, so I don't think that it's a recent GCC improvement, since GCC 4.2.1 is from 2007.
There's no need for this set of tools to be extremely performant, but a reproducible 30% difference seems strange.
Possible reasons:
Clang really is slower than GCC
GCC enables a useful optimisation that Clang doesn't enable (but Clang was tested with -O3, too)
we have some undefined behaviour somewhere, and GCC chooses to optimise this away, while Clang is more strict.
The text was updated successfully, but these errors were encountered:
Observed on macOS Mojave x86-64 with Clang 11.0.0, and OpenBSD/macppc 6.8 with Clang 10.0.1.
scummtr
is approximately 30% faster with GCC than with Clang, when importing a translation.GCC 10.2.0 and GCC 4.2.1 at
-O2
are both faster than Clang at-O2
or-O3
, so I don't think that it's a recent GCC improvement, since GCC 4.2.1 is from 2007.There's no need for this set of tools to be extremely performant, but a reproducible 30% difference seems strange.
Possible reasons:
-O3
, too)The text was updated successfully, but these errors were encountered: