-
Notifications
You must be signed in to change notification settings - Fork 341
[🍒][-Wunsafe-buffer-usage] Warning unsafe libc calls #9287
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
[🍒][-Wunsafe-buffer-usage] Warning unsafe libc calls #9287
Conversation
@swift-ci test |
I somehow can't find @jkorous-apple in the reviewer list. |
Doesn't work for me either hmm. |
Weird, I am here 🤷 |
yeah, that works the best. |
12700fe
to
9ddbe6a
Compare
Rebased, and @swift-ci test |
9ddbe6a
to
99d1407
Compare
Rebased, and @swift-ci test |
[-Wunsafe-buffer-usage] Add warn on unsafe calls to libc functions Warning about calls to libc functions involving buffer access. Warned functions are hardcoded by names. (rdar://117182250) (cherry picked from commit 0fffdeb)
…n libc warnings (llvm#108308) For `snprintf(a, sizeof a, ...)`, the first two arguments form a safe pattern if `a` is a constant array. In such a case, this commit will suppress the warning. (rdar://117182250) (cherry picked from commit ebf25d9)
… Warning Libc functions (llvm#101583)" StringLiteral::getString() is not applicable to strings of wide characters. Added handling for that. (rdar://117182250) (cherry picked from commit 48498ec)
…les (llvm#109496) - Fix a bug in UnsafeBufferUsage.cpp related to casting to PointerType - Suppress -Wunsafe-buffer-usage-in-libc-call for C files (rdar://117182250) (cherry picked from commit 090dc77)
99d1407
to
7d22451
Compare
Rebased, and @swift-ci test |
LGTM |
cherry-picked from
swiftlang/llvm-project/next