en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/cfi/cross-dso/icall/icall.cpp#f156c932 [cfi] Use %ld_flags_rpath_* substitutions in tests (NFC)llvm-svn: 315775 List of files: /llvm-project-15.0.7/compiler-rt/test/cfi/cross-dso/icall/icall.cpp Fri, 13 Oct 2017 23:33:12 +0000 Evgeniy Stepanov <eugeni.stepanov@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/cfi/cross-dso/icall/icall.cpp#22696525 [cfi] Cross-DSO CFI diagnostic mode (compiler-rt part)* add __cfi_slowpath_diag with a 3rd parameter which is a pointer to the diagnostic info for the ubsan handlers.*__cfi_check gets a 3rd parameter as well.* unify vcall/cast/etc and icall diagnostic info format, and merge the handlers to have a single entry point (actually two points due to abort/noabort variants).* testsNote that this comes with a tiny overhead in the non-diag mode:cfi_slowpath must pass 0 as the 3rd argument to cfi_check.llvm-svn: 258744 List of files: /llvm-project-15.0.7/compiler-rt/test/cfi/cross-dso/icall/icall.cpp Mon, 25 Jan 2016 23:34:38 +0000 Evgeniy Stepanov <eugeni.stepanov@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/cfi/cross-dso/icall/icall.cpp#da1cf928 Cross-DSO control flow integrity (compiler-rt part).This is an initial version of the runtime cross-DSO CFI supportlibrary.It contains a number of FIXMEs, ex. it does not support thediagnostic mode nor dlopen/dlclose, but it works and can be tested.Diagnostic mode, in particular, would require some refactoring (we'dlike to gather all CFI hooks in the UBSan library into one functionso that we could easier pass the diagnostic information down to__cfi_check). It will be implemented later.Once the diagnostic mode is in, I plan to create a second testconfiguration to run all existing tests in both modes. For now, thispatch includes only a few new cross-DSO tests.llvm-svn: 255695 List of files: /llvm-project-15.0.7/compiler-rt/test/cfi/cross-dso/icall/icall.cpp Tue, 15 Dec 2015 23:00:33 +0000 Evgeniy Stepanov <eugeni.stepanov@gmail.com>