-
Notifications
You must be signed in to change notification settings - Fork 105
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
Is -fno-strict-aliasing
really necessary?
#143
Comments
At this point I can't remember where these violations were, I just remember compilers throwing warnings about strict aliasing violations in code other than Boost.Log. Maybe these were fixed by now. |
I'm also seeing this
|
@ClaymorePT This is off-topic here, but should be resolved with 77f1e20. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The library builds with
-fno-strict-aliasing
on GCC:log/build/Jamfile.v2
Line 202 in 8a88072
The comment says that it is because of other Boost libraries but does not name them or link bug reports, making it hard to justify the flag. It should be a good thing to re-raise the issue on the libraries that still had not fixed it, as strict aliasing is a severe violation.
The text was updated successfully, but these errors were encountered: