diff options
| author | George Burgess IV <gbiv@google.com> | 2017-07-20 15:13:09 -0700 |
|---|---|---|
| committer | George Burgess IV <gbiv@google.com> | 2017-07-21 11:25:52 -0700 |
| commit | 53c4c8abb009e3381bd8f5d223045eb6985c4f3d (patch) | |
| tree | 32750eda49300dfda3c3815e6496429a6b6975e0 /libc/libstdc++.mips.map | |
| parent | dcdd0e37603215320d4fd175792aeef279a80606 (diff) | |
| download | android_bionic-53c4c8abb009e3381bd8f5d223045eb6985c4f3d.tar.gz android_bionic-53c4c8abb009e3381bd8f5d223045eb6985c4f3d.tar.bz2 android_bionic-53c4c8abb009e3381bd8f5d223045eb6985c4f3d.zip | |
Remove outdated _FORTIFY_SOURCE #undefs
AFAICT, all of these were added prior to the new-style FORTIFY going
in. Because clang saw two definitions of the "same" function, it got
upset. (e.g. 35d937e4eb7b8e0a4e9a113d2f7434d55c0bc056)
Now that our FORTIFY functions are overloads of their library functions,
these undefs can be removed.
(This is a step toward making FORTIFY a library with -U_FORTIFY_SOURCE
on it, as requested in the bug.)
Bug: 12231437
Test: CtsBionicUnitTests. No new failures.
Change-Id: I844ff77106ee2bea72ae1cd0bb85d146939ecd05
Diffstat (limited to 'libc/libstdc++.mips.map')
0 files changed, 0 insertions, 0 deletions