Changes in stack_dynamic_alloca.ll

0df277a1 - [test] Remove some legacy PM tests in llvm/test/Instrumentation/AddressSanitizer

Sun, 05 Sep 2021 19:02:31 +0000

[test] Remove some legacy PM tests in llvm/test/Instrumentation/AddressSanitizer List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

af8c59e0 - Update and improve compiler-rt tests for -mllvm -asan_use_after_return=(never|[runtime]|always).

Tue, 08 Jun 2021 19:45:48 +0000

Update and improve compiler-rt tests for -mllvm -asan_use_after_return=(never|[runtime]|always).In addition: - optionally add global flag to capture compile intent for UAR: __asan_detect_use_after_return_always. The global is a SANITIZER_WEAK_ATTRIBUTE.for issue: https://github.com/google/sanitizers/issues/1394Reviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D103304 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

52ac1147 - LLVM Detailed IR tests for introduction of flag -fsanitize-address-detect-stack-use-after-return-mode.

Thu, 13 May 2021 18:41:43 +0000

LLVM Detailed IR tests for introduction of flag -fsanitize-address-detect-stack-use-after-return-mode.Rework all tests that interact with use after return to correctly handle the case where the mode has been explicitly set to Never or Always.for issue: https://github.com/google/sanitizers/issues/1394Reviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D102462 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

7c2f2762 - [NewPM][ASan] Make ASan tests work under NPM

Sat, 18 Jul 2020 00:49:46 +0000

[NewPM][ASan] Make ASan tests work under NPMUnder NPM, the asan-globals-md analysis is required but cannot be runwithin the asan function pass due to module analyses not being able torun from a function pass. So this pins all tests using "-asan" to thelegacy PM and adds a corresponding RUN line with-passes='require,function(asan)'.Now all tests in Instrumentation/AddressSanitizer pass when-enable-new-pm is by default on.Tests were automatically converted using the following python script andfailures were manually fixed up.import sysfor i in sys.argv: with open(i, 'r') as f: s = f.read() with open(i, 'w') as f: for l in s.splitlines(): if "RUN:" in l and ' -asan -asan-module ' in l and '\\' not in l: f.write(l.replace(' -asan -asan-module ', ' -asan -asan-module -enable-new-pm=0 ')) f.write('\n') f.write(l.replace(' -asan -asan-module ', " -passes='require,function(asan),module(asan-module)' ")) f.write('\n') elif "RUN:" in l and ' -asan ' in l and '\\' not in l: f.write(l.replace(' -asan ', ' -asan -enable-new-pm=0 ')) f.write('\n') f.write(l.replace(' -asan ', " -passes='require,function(asan)' ")) f.write('\n') else: f.write(l) f.write('\n')See https://bugs.llvm.org/show_bug.cgi?id=46611.Reviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D83921 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

c0e6b8ac - IR: Support parsing numeric block ids, and emit them in textual output.

Fri, 22 Mar 2019 18:27:13 +0000

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/AddressSanitizer/stack_dynamic_alloca.ll

5a440d32 - [asan] Test ASan instrumentation for shadow scale value of 5

Fri, 17 Nov 2017 01:15:31 +0000

[asan] Test ASan instrumentation for shadow scale value of 5Add additional RUN clauses to test for -asan-mapping-scale=5 inselective tests, with special CHECK statements where needed.Differential Revision: https://reviews.llvm.org/D39775llvm-svn: 318493 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

869a5ff3 - [ASan] Disable dynamic alloca and UAR detection in presence of returns_twice calls.

Wed, 29 Jul 2015 19:36:08 +0000

[ASan] Disable dynamic alloca and UAR detection in presence of returns_twice calls.Summary:returns_twice (most importantly, setjmp) functions areoptimization-hostile: if local variable is promoted to register, and ischanged between setjmp() and longjmp() calls, this update will beundone. This is the reason why "man setjmp" advises to mark all theselocals as "volatile".This can not be enough for ASan, though: when it replaces static allocawith dynamic one, optionally called if UAR mode is enabled, it adds awhole lot of SSA values, and computations of local variable addresses,that can involve virtual registers, and cause unexpected behavior, whenthese registers are restored from buffer saved in setjmp.To fix this, just disable dynamic alloca and UAR tricks whenever we seea returns_twice call in the function.Reviewers: rnkSubscribers: llvm-commits, kccDifferential Revision: http://reviews.llvm.org/D11495llvm-svn: 243561 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

a79ac14f - [opaque pointer type] Add textual IR support for explicit type parameter to load instruction

Fri, 27 Feb 2015 21:17:42 +0000

[opaque pointer type] Add textual IR support for explicit type parameter to load instructionEssentially the same as the GEP change in r230786.A similar migration script can be used to update test cases, though a few moretest case improvements/changes were required this time around: (r229269-r229278)import fileinputimport sysimport repat = re.compile(r"((?:=|:|^)\s*load (?:atomic )?(?:volatile )?(.*?))(| addrspace$\d+$ *)\*($| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$)")for line in sys.stdin: sys.stdout.write(re.sub(pat, r"\1, \2\3*\4", line))Reviewers: rafael, dexonsmith, grosserDifferential Revision: http://reviews.llvm.org/D7649llvm-svn: 230794 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

8ed1d819 - [asan] Skip promotable allocas to improve performance at -O0

Fri, 27 Feb 2015 03:12:36 +0000

[asan] Skip promotable allocas to improve performance at -O0Currently, the ASan executables built with -O0 are unnecessarily slow.The main reason is that ASan instrumentation pass inserts redundantchecks around promotable allocas. These allocas do not get instrumentedunder -O1 because they get converted to virtual registered by mem2reg.With this patch, ASan instrumentation pass will only instrument nonpromotable allocas, giving us a speedup of 39% on a collection ofbenchmarks with -O0. (There is no measurable speedup at -O1.)llvm-svn: 230724 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll

4b7f413e - [ASan] Change fake stack and local variables handling.

Thu, 11 Dec 2014 21:53:03 +0000

[ASan] Change fake stack and local variables handling.This commit changes the way we get fake stack from ASan runtime(to find use-after-return errors) and the way we represent localvariables: - __asan_stack_malloc function now returns pointer to newly allocated fake stack frame, or NULL if frame cannot be allocated. It doesn't take pointer to real stack as an input argument, it is calculated inside the runtime. - __asan_stack_free function doesn't take pointer to real stack as an input argument. Now this function is never called if fake stack frame wasn't allocated. - __asan_init version is bumped to reflect changes in the ABI. - new flag "-asan-stack-dynamic-alloca" allows to store all the function local variables in a dynamic alloca, instead of the static one. It reduces the stack space usage in use-after-return mode (dynamic alloca will not be called if the local variables are stored in a fake stack), and improves the debug info quality for local variables (they will not be described relatively to %rbp/%rsp, which are assumed to be clobbered by function calls). This flag is turned off by default for now, but I plan to turn it on after more testing.llvm-svn: 224062 List of files: /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/stack_dynamic_alloca.ll