en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#86d1a0b3 [test] Remove some legacy PM tests in llvm/test/Instrumentation List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Sun, 05 Sep 2021 18:51:19 +0000 Arthur Eubanks <aeubanks@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#9b1539be [NewPM][Sancov] Pin RUN lines with -sancov to legacy PMSince the NPM pass is named sancov-module, not sancov.This makes all tests under Instrumentation/SanitizerCoverage pass when-enable-new-pm is on by default.Reviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D84687 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Mon, 27 Jul 2020 18:31:34 +0000 Arthur Eubanks <aeubanks@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#eca01b03 [NewPM][Sancov] Make Sancov a Module Pass instead of 2 PassesThis patch merges the sancov module and funciton passes into one module pass.The reason for this is because we ran into an out of memory error whenattempting to run asan fuzzer on some protobufs (pc.cc files). I traced the OOMerror to the destructor of SanitizerCoverage where we only callappendTo[Compiler]Used which calls appendToUsedList. I'm not sure where preciselyin appendToUsedList causes the OOM, but I am able to confirm that it's callingthis function *repeatedly* that causes the OOM. (I hacked sancov a bit such thatI can still create and destroy a new sancov on every function run, but only callappendToUsedList after all functions in the module have finished. This passes, butwhen I make it such that appendToUsedList is called on every sancov destruction,we hit OOM.)I don't think the OOM is from just adding to the SmallSet and SmallVector insideappendToUsedList since in either case for a given module, they'll have the samemax size. I suspect that when the existing llvm.compiler.used global is erased,the memory behind it isn't freed. I could be wrong on this though.This patch works around the OOM issue by just calling appendToUsedList at theend of every module run instead of function run. The same amount of constantsstill get added to llvm.compiler.used, abd we make the pass usage and logicsimpler by not having any inter-pass dependencies.Differential Revision: https://reviews.llvm.org/D66988llvm-svn: 370971 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Wed, 04 Sep 2019 20:30:29 +0000 Leonard Chan <leonardchan@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#007f674c Reland the "[NewPM] Port Sancov" patch from rL365838. No functionalchanges were made to the patch since then.--------[NewPM] Port SancovThis patch contains a port of SanitizerCoverage to the new pass manager. This one's a bit hefty.Changes:- Split SanitizerCoverageModule into 2 SanitizerCoverage for passing over functions and ModuleSanitizerCoverage for passing over modules.- ModuleSanitizerCoverage exists for adding 2 module level calls to initialization functions but only if there's a function that was instrumented by sancov.- Added legacy and new PM wrapper classes that own instances of the 2 new classes.- Update llvm tests and add clang tests.llvm-svn: 367053 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Thu, 25 Jul 2019 20:53:15 +0000 Leonard Chan <leonardchan@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#006cf8c0 Added address-space mangling for stack related intrinsicsModified the following 3 intrinsics:int_addressofreturnaddress,int_frameaddress & int_sponentry.Reviewed By: arsenmDifferential Revision: https://reviews.llvm.org/D64561llvm-svn: 366679 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Mon, 22 Jul 2019 12:42:48 +0000 Christudasan Devadasan <Christudasan.Devadasan@amd.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#bb147aab Revert "[NewPM] Port Sancov"This reverts commit 5652f35817f07b16f8b3856d594cc42f4d7ee29c.llvm-svn: 366153 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Mon, 15 Jul 2019 23:18:31 +0000 Leonard Chan <leonardchan@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#5652f358 [NewPM] Port SancovThis patch contains a port of SanitizerCoverage to the new pass manager. This one's a bit hefty.Changes:- Split SanitizerCoverageModule into 2 SanitizerCoverage for passing over functions and ModuleSanitizerCoverage for passing over modules.- ModuleSanitizerCoverage exists for adding 2 module level calls to initialization functions but only if there's a function that was instrumented by sancov.- Added legacy and new PM wrapper classes that own instances of the 2 new classes.- Update llvm tests and add clang tests.Differential Revision: https://reviews.llvm.org/D62888llvm-svn: 365838 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Thu, 11 Jul 2019 22:35:40 +0000 Leonard Chan <leonardchan@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#c0e6b8ac IR: Support parsing numeric block ids, and emit them in textual output.Just as as llvm IR supports explicitly specifying numeric value idsfor instructions, and emits them by default in textual output, now dothe same for blocks.This is a slightly incompatible change in the textual IR format.Previously, llvm would parse numeric labels as string names. E.g. define void @f() { br label %"55" 55: ret void }defined a label *named* "55", even without needing to be quoted, whilethe reference required quoting. Now, if you intend a block label whichlooks like a value number to be a name, you must quote it in thedefinition too (e.g. `"55":`).Previously, llvm would print nameless blocks only as a comment, andwould omit it if there was no predecessor. This could cause confusionfor readers of the IR, just as unnamed instructions did prior to theaddition of "%5 = " syntax, back in 2008 (PR2480).Now, it will always print a label for an unnamed block, with theexception of the entry block. (IMO it may be better to print it forthe entry-block as well. However, that requires updating many moretests.)Thus, the following is supported, and is the canonical printing: define i32 @f(i32, i32) { %3 = add i32 %0, %1 br label %4 4: ret i32 %3 }New test cases covering this behavior are added, and other testsupdated as required.Differential Revision: https://reviews.llvm.org/D58548llvm-svn: 356789 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Fri, 22 Mar 2019 18:27:13 +0000 James Y Knight <jyknight@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#034126e5 [SanitizeCoverage] Enable stack-depth coverage for -fsanitize=fuzzerSummary:- Don't sanitize __sancov_lowest_stack.- Don't instrument leaf functions.- Add CoverageStackDepth to Fuzzer and FuzzerNoLink.- Only enable on Linux.Reviewers: vitalybuka, kcc, george.karpenkovReviewed By: kccSubscribers: kubamracek, cfe-commits, llvm-commits, hiradityaDifferential Revision: https://reviews.llvm.org/D37156llvm-svn: 312185 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Wed, 30 Aug 2017 22:49:31 +0000 Matt Morehouse <mascasa@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#ba2e61b3 Revert "[SanitizeCoverage] Enable stack-depth coverage for -fsanitize=fuzzer"This reverts r312026 due to bot breakage.llvm-svn: 312047 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Tue, 29 Aug 2017 21:56:56 +0000 Matt Morehouse <mascasa@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#2ad8d948 [SanitizeCoverage] Enable stack-depth coverage for -fsanitize=fuzzerSummary:- Don't sanitize __sancov_lowest_stack.- Don't instrument leaf functions.- Add CoverageStackDepth to Fuzzer and FuzzerNoLink.- Disable stack depth tracking on Mac.Reviewers: vitalybuka, kcc, george.karpenkovReviewed By: kccSubscribers: kubamracek, cfe-commits, llvm-commits, hiradityaDifferential Revision: https://reviews.llvm.org/D37156llvm-svn: 312026 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Tue, 29 Aug 2017 19:48:12 +0000 Matt Morehouse <mascasa@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#6ec7595b Revert "[SanitizeCoverage] Enable stack-depth coverage for -fsanitize=fuzzer"This reverts r311801 due to a bot failure.llvm-svn: 311803 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Fri, 25 Aug 2017 22:01:21 +0000 Matt Morehouse <mascasa@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#f42bd313 [SanitizeCoverage] Enable stack-depth coverage for -fsanitize=fuzzerSummary:- Don't sanitize __sancov_lowest_stack.- Don't instrument leaf functions.- Add CoverageStackDepth to Fuzzer and FuzzerNoLink.Reviewers: vitalybuka, kccReviewed By: kccSubscribers: cfe-commits, llvm-commits, hiradityaDifferential Revision: https://reviews.llvm.org/D37156llvm-svn: 311801 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Fri, 25 Aug 2017 21:18:29 +0000 Matt Morehouse <mascasa@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#b1fa8255 [SanitizerCoverage] Optimize stack-depth instrumentation.Summary:Use the initialexec TLS type and eliminate calls to the TLSwrapper. Fixes the sanitizer-x86_64-linux-fuzzer bot failure.Reviewers: vitalybuka, kccReviewed By: kccSubscribers: hiraditya, llvm-commitsDifferential Revision: https://reviews.llvm.org/D37026llvm-svn: 311490 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Tue, 22 Aug 2017 21:28:29 +0000 Matt Morehouse <mascasa@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll#5c7fc769 [SanitizerCoverage] Add stack depth tracing instrumentation.Summary:Augment SanitizerCoverage to insert maximum stack depth tracing foruse by libFuzzer. The new instrumentation is enabled by the flag-fsanitize-coverage=stack-depth and is compatible with the existingtrace-pc-guard coverage. The user must also declare the followingglobal variable in their code: thread_local uintptr_t __sancov_lowest_stackhttps://bugs.llvm.org/show_bug.cgi?id=33857Reviewers: vitalybuka, kccReviewed By: vitalybukaSubscribers: kubamracek, hiraditya, cfe-commits, llvm-commitsDifferential Revision: https://reviews.llvm.org/D36839llvm-svn: 311186 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/SanitizerCoverage/stack-depth.ll Fri, 18 Aug 2017 18:43:30 +0000 Matt Morehouse <mascasa@google.com>