-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix -Wunsafe-buffer-usage
warnings
#81577
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @hoyosjs Issue DetailsClang 16 has introduced buffer hardening https://discourse.llvm.org/t/rfc-c-buffer-hardening/65734 which #81573 is suppressing. Filing this issue so we remember to fix the violations and remove suppression.
|
On Alpine edge (clang 16), I also get:
Applied the following workaround: diff --git a/src/runtime/eng/native/configurecompiler.cmake b/src/runtime/eng/native/configurecompiler.cmake
index c9a54547c0a..931da2cae5b 100644
--- a/src/runtime/eng/native/configurecompiler.cmake
+++ b/src/runtime/eng/native/configurecompiler.cmake
@@ -488,6 +488,7 @@ if (CLR_CMAKE_HOST_UNIX)
# other clang 16.0 suppressions
add_compile_options(-Wno-single-bit-bitfield-constant-conversion)
add_compile_options(-Wno-cast-function-type-strict)
+ add_compile_options(-Wno-incompatible-function-pointer-types-strict)
else()
add_compile_options(-Wno-uninitialized)
add_compile_options(-Wno-strict-aliasing) |
Clang 16 has introduced buffer hardening https://discourse.llvm.org/t/rfc-c-buffer-hardening/65734 which #81573 is suppressing. Filing this issue so we remember to fix the violations and remove suppression.
The text was updated successfully, but these errors were encountered: