search for: shadowcallstack

Hi all, I'm in the process of trying to port ShadowCallStack from the legacy pass manager to the new one. I ran into an issue though where it seems I cannot link against anything I added in ShadowCallStack.cpp when trying to build c-index-test (via just running ninja check-all). I think the reason for this is because nothing under lib/Target/X86/ is a part o...

...which holds an instance to the first class. The new PM analysis holds an instance of this first class also. I'm not sure though if there are new PM equivalents for the addPreserved analyses that MachineFunctionPass has under it's getAnalysisUsage. I can't figure out though how to port ShadowCallStack specifically, assuming I completed all the necessary work for enabling MachineFunctionPass in new PM, but I imagine that I may have missed a few things that I didn't account for. I can share what I have currently if you would like to see. - Leonard On Tue, Jan 8, 2019 at 10:37 AM Craig Topper...

...s been committed. As previously [described](http://lists.llvm.org/pipermail/llvm-dev/2018-March/121814.html) on llvm-dev, this tool allows the automatic measurement of instruction scheduling properties such as latency and the number of micro-ops. [r329156](https://reviews.llvm.org/rL329156). * The ShadowCallStack pass has been added. Functions marked with the `shadowcallstack` attribute will be instrumented to check in the prolog/epilog that the return address has not been corrupted during execution. This is supported on both X86-64 and AArch64. [r329139](https://reviews.llvm.org/rL329139),[r329236](https:/...

...izes by matching up function names, and use this annotated call graph to find the execution path with the largest stack. Backends: We plan to support the x86-64 and aarch64 architectures; adding other architectures should be straight-forward. Fancy stacks: We plan to support using SafeStack & ShadowCallStack. Hand-written assembly: The Zircon codebase contains a nontrivial amount of hand-written assembly which uses stack space. We will manually audit the stack usage of assembly code, and provide it to the analysis in a lookup table. Indirect Function Calls & Recursion: We hope to not run into too...

...ion: GNU ld -- Linker detection: GNU ld -- Builtin supported architectures: x86_64 -- Generated Sanitizer SUPPORTED_TOOLS list on "Linux" is "asan;lsan;msan;tsan;ubsan" -- sanitizer_common tests on "Linux" will run against "asan;lsan;msan;tsan;ubsan" -- check-shadowcallstack does nothing. -- Looking for sys/resource.h -- Looking for sys/resource.h - found -- Clang version: 9.0.0 -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Failed -- Looking for include file sys/inotify.h -- Looking for include fil...

...detection: LLD -- Linker detection: LLD -- Builtin supported architectures: x86_64 -- Generated Sanitizer SUPPORTED_TOOLS list on "Linux" is "asan;lsan;msan;tsan;ubsan" -- sanitizer_common tests on "Linux" will run against "asan;lsan;msan;tsan;ubsan" -- check-shadowcallstack does nothing. -- Looking for sys/resource.h -- Looking for sys/resource.h - found -- Clang version: 9.0.0 -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Success -- Looking for include file sys/inotify.h -- Looking for include fi...