Conversation
This flag includes warnings that are not intended for end-users to use - for example it includes the experimental -Wunsafe-buffer-usage flag which only makes sense when attempting to use a safe subset of C++. See https://quuxplusone.github.io/blog/2018/12/06/dont-use-weverything/ for a more in-depth explanation of the problems with this flag.
|
We've had Adding a cmake option to remove |
|
I agree with @dj2 here. I believe the -Wunsafe-buffer-usage flag was proven to have a buggy implementation. |
I should be clear. I did read that blog post and I still think this project should turn it on. I think the example given in the blog post is not persuasive. I would want to add the new line at the end of file anyway. |
|
The problem is when amber is used in other projects like VK-GL-CTS; if we ever want to use a new compiler with the vulkan conformance tests, for correctness every version of amber that's used in a released version of VK-GL-CTS needs to have the flag added, and rolled into that version of VK-GL-CTS. |
|
Right, that's why I suggest a cmake flag to turn off |
This flag includes warnings that are not intended for end-users to use - for example it includes the experimental -Wunsafe-buffer-usage flag which only makes sense when attempting to use a safe subset of C++.
See https://quuxplusone.github.io/blog/2018/12/06/dont-use-weverything/ for a more in-depth explanation of the problems with this flag.