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
Build fails with strict-aliasing violations #4413
Comments
Recent laf main code don't has reinterpret_cast invocations, so these errors may be fixed by fetching recent laf codebase. |
My report is about 1.3.6 Which part of the commits since 1.3.6 do you believe solved this issue? |
Sorry, misread source code. Proposed PR aseprite/laf#84 intended to fix this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to build with the following *FLAGS to optimize the build:
-flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing
The -Werror=* flags are important to detect cases where the compiler can try to optimize based on assuming UB cannot happen, and miscompile code that has UB in it. strict-aliasing issues are always bad but LTO can make them even worse.
I got this error:
Originally reported downstream: https://bugs.gentoo.org/924692
Full build log: build.log
The text was updated successfully, but these errors were encountered: