search for: module_ctor

At 167457 on x86_64-apple-darwin12, I am seeing a slew of AddressSanitizer failures due to unresolved symbols such as... Exit Code: 1 Command Output (stderr): -- Undefined symbols for architecture x86_64: "___asan_init", referenced from: _asan.module_ctor in shared-lib-test-so-moBSTe.o "___asan_register_globals", referenced from: _asan.module_ctor in shared-lib-test-so-moBSTe.o "___asan_report_load4", referenced from: _inc in shared-lib-test-so-moBSTe.o "___asan_report_store4", referenced from: _...

...SecEnd->setVisibility(GlobalValue::HiddenVisibility); + appendToUsed(M, {SecStart, SecEnd}); return std::make_pair(SecStart, SecEnd); } I'm trying it out now. Kostya Serebryany <kcc at google.com> writes: > With -Wl,-gc-sections I get this: > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x1b): > undefined reference to `__start___sancov_pcs' > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x20): > undefined reference to `__stop___sancov_pcs' > > > > On Thu, Aug 24, 2017 at 3:07 PM, George Karpenkov <ekarpenkov at ap...

> On Aug 24, 2017, at 2:55 PM, Kostya Serebryany <kcc at google.com> wrote: > > Interesting. > This is a relatively new addition (fsanitize-coverage=pc-tables, which is now a part of -fsanitize=fuzzer). > The tests worked (did they? On Mac?) so I thought everything is ok. For tests we never compile the tested target with -O3 (and that wouldn’t be sufficient), and for

...ts llvm.used has no effect on the object file (only on the optimizer). Is there a simple way to reproduce the link failure? Peter > >> >> Kostya Serebryany <kcc at google.com> writes: >> > With -Wl,-gc-sections I get this: >> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x1b): >> > undefined reference to `__start___sancov_pcs' >> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x20): >> > undefined reference to `__stop___sancov_pcs' >> > >> > >> > >> > On Thu,...

...57 on x86_64-apple-darwin12, I am seeing a slew of > AddressSanitizer failures due to > unresolved symbols such as... > > Exit Code: 1 > Command Output (stderr): > -- > Undefined symbols for architecture x86_64: > "___asan_init", referenced from: > _asan.module_ctor in shared-lib-test-so-moBSTe.o > "___asan_register_globals", referenced from: > _asan.module_ctor in shared-lib-test-so-moBSTe.o > "___asan_report_load4", referenced from: > _inc in shared-lib-test-so-moBSTe.o > "___asan_report_store4",...

...eing a slew of >> AddressSanitizer failures due to >> unresolved symbols such as... >> >> Exit Code: 1 >> Command Output (stderr): >> -- >> Undefined symbols for architecture x86_64: >> "___asan_init", referenced from: >> _asan.module_ctor in shared-lib-test-so-moBSTe.o >> "___asan_register_globals", referenced from: >> _asan.module_ctor in shared-lib-test-so-moBSTe.o >> "___asan_report_load4", referenced from: >> _inc in shared-lib-test-so-moBSTe.o >> "___asan_...

Hi, I am trying to execute a simple hello world program compiled like so: path/to/compiled/clang -o test --target=aarch64-linux-gnu -march=armv8.5-a -fsanitize=hwaddress --sysroot=/usr/aarch64-linux-gnu/ -L/usr/lib/gcc/aarch64-linux-gnu/10.1.0/ -g test.c However, when I look at the disassembly, there is an unknown instruction listed at 0x2d51c: 000000000002d4c0 main: 2d4c0: ff c3 00 d1

....20170105". Peter > > > > > >> >> Peter >> >> >>> >>>> >>>> Kostya Serebryany <kcc at google.com> writes: >>>> > With -Wl,-gc-sections I get this: >>>> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x1b): >>>> > undefined reference to `__start___sancov_pcs' >>>> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x20): >>>> > undefined reference to `__stop___sancov_pcs' >>>> > >>>>...

...>> >>> >>>> >>> >>>>> >>> >>>>> Kostya Serebryany <kcc at google.com> writes: >>> >>>>> > With -Wl,-gc-sections I get this: >>> >>>>> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor] >>> +0x1b): >>> >>>>> > undefined reference to `__start___sancov_pcs' >>> >>>>> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor] >>> +0x20): >>> >>>>> > undefined...

...uish from non-pass options. > > regards, > Fedor. > > > Cheers, > Philip > >> >> doesn't produce the same IR as >> >> `opt < %s -asan -asan-module -S` >> >> More specifically, the only thing missing seems to be the >> `asan.module_ctor` that should get added to the global ctors list. >> What I'm not sure of is if I'm missing something when I made the new >> pass or it's something in the pipeline regarding which passes run >> first between both PMs. I could just make an AddressSanitizerModule >>...

...t;> Peter > >>> > >>> > >>>> > >>>>> > >>>>> Kostya Serebryany <kcc at google.com> writes: > >>>>> > With -Wl,-gc-sections I get this: > >>>>> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ > ctor]+0x1b): > >>>>> > undefined reference to `__start___sancov_pcs' > >>>>> > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ > ctor]+0x20): > >>>>> > undefined reference to `__stop___sancov_pcs'...

...san-module -S` > asan-module is another ModulePass, not a commandline option. You can't mix that like this. Cheers, Philip > doesn't produce the same IR as > > `opt < %s -asan -asan-module -S` > > More specifically, the only thing missing seems to be the > `asan.module_ctor` that should get added to the global ctors list. > What I'm not sure of is if I'm missing something when I made the new > pass or it's something in the pipeline regarding which passes run > first between both PMs. I could just make an AddressSanitizerModule > pass for the ne...

Specifically, the test is causing a link to occur for CGO stuff. It has been running 8 minutes now with Gold, and is producing a 400mb .o file afaict: % du -hs /tmp/go-build703430446/ llvm.org/llvm/bindings/go/llvm/_test/_obj_test/_cgo_.o 397M /tmp/go-build703430446/ llvm.org/llvm/bindings/go/llvm/_test/_obj_test/_cgo_.o What am I doing wrong here? -------------- next part -------------- An

...t/build/llvm/lib/Target/X86/MCTargetDesc/X86MCAsmInfo.cpp:31:1' (0x2ef4140) of size 600 registered at: #0 0x4c63fd in __asan_register_globals.part.15 /mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm/projects/compiler-rt/lib/asan/asan_globals.cc:338 #1 0x9d3f9b in asan.module_ctor (/mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm_build_asan/unittests/MC/MCTests+0x9d3f9b) The reports seems correct. The flag object AsmWriterFlavor is used before it is initialized in initialization of some other global object. This makes the asan bot red... :( Thanks, --kcc...

...compiler-rt/lib/msan/../sanitizer_common/sanitizer_common_interceptors.inc:5902 #17 __msan::InitializeInterceptors () at ../projects/compiler-rt/lib/msan/msan_interceptors.cc:1471 #18 0x000000000043f4c5 in __msan_init () at ../projects/compiler-rt/lib/msan/msan.cc:386 #19 0x000000000048d586 in msan.module_ctor () #20 0x000000000048d5dd in __libc_csu_init () #21 0x00007ffff6f18220 in __libc_start_main () from /usr/lib/libc.so.6 #22 0x00000000004192da in _start () (gdb) When I compile it with clang 3.8.1 it fails in a different spot but still in __interception::GetRealFunctionAddress: $ clang -fsanitize...

Frontends _are_ using PassBuilder, but they need to hook into the default pipeline creation to insert the sanitizer passes. On Tue, Sep 25, 2018 at 12:15 PM Fedor Sergeev <fedor.sergeev at azul.com> wrote: > Hmm... frontends should be using PassBuilder anyway. > And if they are using PassBuilder then they are using PassRegistry.def as > well - all the >

> On Sep 1, 2016, at 9:20 PM, Greg Parker <gparker at apple.com> wrote: > >> On Sep 1, 2016, at 9:06 PM, llvm.buildmaster at lab.llvm.org wrote: >> >> The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-fast while building llvm. >> Full details are available at: >>