Is `-fno-strict-aliasing` really necessary?
Open
- Dominant language
- C++
- Stars
- 211
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
The library builds with `-fno-strict-aliasing` on GCC:
https://github.com/boostorg/log/blob/8a880720be5a990fdd0f864244bfff1a39a69d83/build/Jamfile.v2#L202
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.