diff options
| author | Maxim Ostapenko <m.ostapenko@samsung.com> | 2016-11-16 11:13:19 +0000 |
|---|---|---|
| committer | Maxim Ostapenko <chefmax@gcc.gnu.org> | 2016-11-16 13:13:19 +0200 |
| commit | 511c8687a8754142bb4434acfa7a2b0278d8f3d7 (patch) | |
| tree | ba2f184fd344d51d38b6283f41122708328b876a /libsanitizer/HOWTO_MERGE | |
| parent | 024f701ca1dc69ff3d6a3d0ec727debc224018f0 (diff) | |
re PR sanitizer/78307 (missing symbols in libubsan without changing the soname)
PR sanitizer/78307
* ubsan/ubsan_handlers.cc (__ubsan_handle_cfi_bad_icall): New function.
( __ubsan_handle_cfi_bad_icall_abort): Likewise.
* ubsan/ubsan_handlers.h (struct CFIBadIcallData): New type.
* ubsan/ubsan_handlers_cxx.cc (__ubsan_handle_cfi_bad_type): New
function.
(__ubsan_handle_cfi_bad_type_abort): Likewise.
* ubsan/ubsan_handlers_cxx.h (struct CFIBadTypeData): New type.
(__ubsan_handle_cfi_bad_type): Export function.
(__ubsan_handle_cfi_bad_type_abort): Likewise.
* HOWTO_MERGE: Update documentation.
From-SVN: r242478
Diffstat (limited to 'libsanitizer/HOWTO_MERGE')
| -rw-r--r-- | libsanitizer/HOWTO_MERGE | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/libsanitizer/HOWTO_MERGE b/libsanitizer/HOWTO_MERGE index d0eca40ec06..81121aa385f 100644 --- a/libsanitizer/HOWTO_MERGE +++ b/libsanitizer/HOWTO_MERGE @@ -11,7 +11,8 @@ general list of actions required to perform the merge: in corresponding CMakeLists.txt and config-ix.cmake files from compiler-rt source directory. * Apply all needed GCC-specific patches to libsanitizer (note that some of - them might be already included to upstream). + them might be already included to upstream). The list of these patches is stored + into LOCAL_PATCHES file. * Apply all necessary compiler changes. Be especially careful here, you must not break ABI between compiler and library. You can reveal these changes by inspecting the history of AddressSanitizer.cpp and ThreadSanitizer.cpp files @@ -37,3 +38,4 @@ general list of actions required to perform the merge: in libasan, configure/Makefile changes). The review process has O(N^2) complexity, so you would simplify and probably speed up the review process by doing this. * Send your patches for review to GCC Patches Mailing List (gcc-patches@gcc.gnu.org). +* Update LOCAL_PATCHES file when you've committed the whole patch set with new revisions numbers. |