diff options
author | George Burgess IV <gbiv@google.com> | 2017-04-18 18:28:19 -0700 |
---|---|---|
committer | George Burgess IV <gbiv@google.com> | 2017-04-19 18:46:44 +0000 |
commit | 31e5a35f3d403ffa4ffe0215f9664d08fb749ada (patch) | |
tree | 3304b1cfa2e6c55c556f908d522be14ddfd76990 /libc/stdio/stdio_ext.cpp | |
parent | 7b37fa9384cb9ca9a95928af45b03b2bc9fe815c (diff) |
libc: fix typo in __RENAME macro
Apparently __strncpy_real redirects to strcpy instead of strncpy for GCC
builds. This is bad, and it confused a project compiled by GCC that uses
strcpy.
I audited all of the FORTIFY-related __RENAMEs both manually and with a
script I hacked together; they all look correct aside from this one.
FWIW, with the cleaned up clang FORTIFY, lots of the `void foo()
__RENAME(foo)` will just become `void foo()` if this last thing I'm
working on gets through review.
Bug: 35329524
Test: Previously broken project now seems to work. Bullhead and Ryu
both build + boot.
Change-Id: Ib18ee3535ae31eb7e8ae846dc012f9b64cac80bf
Diffstat (limited to 'libc/stdio/stdio_ext.cpp')
0 files changed, 0 insertions, 0 deletions