Changes in stack-depth-variable-declared-by-user.ll

fe7f5f9126cea9ceba703d5bd07b766181f2bd72 - [NFC][Intrumentation] Don't brake long RUN: lines (#112281)

Tue, 15 Oct 2024 17:45:42 +0000

[NFC][Intrumentation] Don't brake long RUN: lines (#112281)I find multiline 'RUN:' statements hard to read. ` *\\\n; RUN: *` -> ` ` for ./llvm/test/Instrumentation/ List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

edb2fc6dab2cf04779959829434e9e8572d48a26 - [llvm] Remove explicit -opaque-pointers flag from tests (NFC)

Wed, 12 Jul 2023 12:19:34 +0000

[llvm] Remove explicit -opaque-pointers flag from tests (NFC)Opaque pointers mode is enabled by default, no need to explicitlyenable it. List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

90ec6dff860f4ec9cb89041b6e2a671cc3ce8f47 - [OpaquePtr] Forbid mixing typed and opaque pointers

Sat, 04 Sep 2021 10:18:52 +0000

[OpaquePtr] Forbid mixing typed and opaque pointersCurrently, opaque pointers are supported in two forms: The-force-opaque-pointers mode, where all pointers are opaque andtyped pointers do not exist. And as a simple ptr type that cancoexist with typed pointers.This patch removes support for the mixed mode. You either gettyped pointers, or you get opaque pointers, but not both. In the(current) default mode, using ptr is forbidden. In -opaque-pointersmode, all pointers are opaque.The motivation here is that the mixed mode introduces additionalissues that don't exist in fully opaque mode. D105155 is an exampleof a design problem. Looking at D109259, it would probably needadditional work to support mixed mode (e.g. to generate GEPs fortyped base but opaque result). Mixed mode will also end upinserting many casts between i8* and ptr, which would requiresignificant additional work to consistently avoid.I don't think the mixed mode is particularly valuable, as itdoesn't align with our end goal. The only thing I've found it tobe moderately useful for is adding some opaque pointer tests inbetween typed pointer tests, but I think we can live without that.Differential Revision: https://reviews.llvm.org/D109290 List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

86d1a0b30684f2ab8ec33f0b6fa3d05e4bada0c8 - [test] Remove some legacy PM tests in llvm/test/Instrumentation

Sun, 05 Sep 2021 18:51:19 +0000

[test] Remove some legacy PM tests in llvm/test/Instrumentation List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

c4de78e91c9341b5b1abf927da15e0956a484b79 - [SanitizerCoverage] Fix global type check with opaque pointers

Tue, 29 Jun 2021 18:29:10 +0000

[SanitizerCoverage] Fix global type check with opaque pointersThe code was previously relying on the fact that an incorrectlytyped global would result in the insertion of a BitCast constantexpression. With opaque pointers, this is no longer the case, sowe should check the type explicitly. List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

9b1539be406da714ab7cbb379575f67d82b874b2 - [NewPM][Sancov] Pin RUN lines with -sancov to legacy PM

Mon, 27 Jul 2020 18:31:34 +0000

[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/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

eca01b031d44da54239d9956ba0acc7cf2f7798b - [NewPM][Sancov] Make Sancov a Module Pass instead of 2 Passes

Wed, 04 Sep 2019 20:30:29 +0000

[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/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

007f674c6a4e47cf3a290c0e2d5ba96483d0f8dc - Reland the "[NewPM] Port Sancov" patch from rL365838. No functional

Thu, 25 Jul 2019 20:53:15 +0000

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/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

bb147aabc68c366cff4ac5f1713b7b138a3b0fe0 - Revert "[NewPM] Port Sancov"

Mon, 15 Jul 2019 23:18:31 +0000

Revert "[NewPM] Port Sancov"This reverts commit 5652f35817f07b16f8b3856d594cc42f4d7ee29c.llvm-svn: 366153 List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

5652f35817f07b16f8b3856d594cc42f4d7ee29c - [NewPM] Port Sancov

Thu, 11 Jul 2019 22:35:40 +0000

[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/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll

29ac3a5b822ba8c097a3ae78d983cdb94da43dd4 - [SanitizerCoverage] Clang crashes if user declares `__sancov_lowest_stack` variable

Mon, 04 Feb 2019 22:06:30 +0000

[SanitizerCoverage] Clang crashes if user declares `__sancov_lowest_stack` variableSummary:If the user declares or defines `__sancov_lowest_stack` with anunexpected type, then `getOrInsertGlobal` inserts a bitcast and thefollowing cast fails:```Constant *SanCovLowestStackConstant = M.getOrInsertGlobal(SanCovLowestStackName, IntptrTy);SanCovLowestStack = cast(SanCovLowestStackConstant);```This variable is a SanitizerCoverage implementation detail and the usershould generally never have a need to access it, so we emit an errornow.rdar://problem/44143130Reviewers: morehouseDifferential Revision: https://reviews.llvm.org/D57633llvm-svn: 353100 List of files: /llvm-project/llvm/test/Instrumentation/SanitizerCoverage/stack-depth-variable-declared-by-user.ll