https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007
--- Comment #25 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #24 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > (In reply to fxcoud...@gmail.com from comment #19) >> I haven’t yet tested Xcode 13.3 myself, and have only followed the PRs from >> far away. Are there any issues (SDK, linker, or otherwise) that we need to >> report to Apple? Or that are already reported but we want taken more >> seriously? > > Do they use [[clang::unsafe_buffer_usage]] then if __has_safe_buffers is > defined > even in -std=c11 etc. modes in the headers? they do AFAICS: their <sys/cdefs.h> has no provision for different C std versions (except the obvious like not using restrict before C99). The section in question is #if __has_cpp_attribute(clang::unsafe_buffer_usage) #define __has_safe_buffers 1 #define __unsafe_buffer_usage [[clang::unsafe_buffer_usage]] #elif __has_attribute(unsafe_buffer_usage) #define __has_safe_buffers 1 #define __unsafe_buffer_usage __attribute__((__unsafe_buffer_usage__)) #else #define __has_safe_buffers 0 #define __unsafe_buffer_usage #endif with a long comment explaining the use with clang -Wunsafe-buffer-usage.
