diff options
| author | George Burgess IV <gbiv@google.com> | 2017-04-18 18:28:19 -0700 |
|---|---|---|
| committer | Elliott Hughes <enh@google.com> | 2017-04-19 13:38:52 -0700 |
| commit | 07e75fe9a1cbf323b5de168448583ed66211efe0 (patch) | |
| tree | 0e83e0235ac818528648c8b432a1d50cb73a8bbb /libc/stdio/stdio_ext.cpp | |
| parent | a0e5d06c80c4c7cd8ae96e75d6b17c696a97a21d (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.
(cherry picked from commit 31e5a35f3d403ffa4ffe0215f9664d08fb749ada)
Change-Id: I790a42f2cf2f7b8e003faa4df9135db22a2e20db
Diffstat (limited to 'libc/stdio/stdio_ext.cpp')
0 files changed, 0 insertions, 0 deletions