search for: asan_noinst_test

...olchains/lib64" -DLLVM_ENABLE_PROJECTS='clang;compiler-rt;libcxx;libcxxabi' ../llvm ninja check-asan # Get another coffee After about 30 minutes, the ninja command fails with an error about how the string header isn't found: FAILED: projects/compiler-rt/lib/asan/tests/ASAN_NOINST_TEST_OBJECTS.asan_noinst_test.cc.x86_64-inline.o cd /usr/local/google/home/jacobsa/clients/llvm-project/build/projects/compiler-rt/lib/asan/tests && /usr/local/google/home/jacobsa/clients/llvm-project/build/./bin/clang -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -Wex...

...ng compiler errors for compiler-rt sources as below. Do not know, if the first argument to IsNullLiteralHelper() is to be passed as '0' instead of false, in the below lines. ========================================== /local/home/mahesha/src/12th_Sep/llvm/projects/compiler-rt/lib/asan/tests/asan_noinst_test.cc: In member function ‘virtual void AddressSanitizerInterface_GetAllocatedSizeAndOwnershipTest_Test::TestBody()’: /local/home/mahesha/src/12th_Sep/llvm/projects/compiler-rt/lib/asan/tests/asan_noinst_test.cc:373:3: error: converting ‘false’ to pointer type for argument 1 of ‘char testing::internal...

...g. I can pursue either of these options, but I'd like to know which the ASan folks would be most interested in working with. Second, it would be extremely helpful to have a very firm separation between bucket #1 and bucket #2. Currently, there is one collection of tests clearly in bucket #1 (asan_noinst_test.cc), and plenty of tests clearly in bucket #2, but there seems to be quite a bit of overlap as well. For example, I would naively expect asan_interface_test.cc to not require instrumentation -- it almost exclusively directly calls the runtime. But it is currently being compiled with instrumentation...

On Sat, Oct 13, 2012 at 1:09 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com> > wrote: > > I'm seeing this too. CC'ing the author ubsan stuff. > > > > Richard, I know you were OK with only supporting Clang-bootstraps, but I > > don't think that's terribly viable

...be most interested in working with. > > Second, it would be extremely helpful to have a very firm separation > between bucket #1 and bucket #2. > (answering parts at a time) Agree. I am going to fix that now. > Currently, there is one collection of tests clearly in bucket #1 > (asan_noinst_test.cc), and plenty of tests clearly in bucket #2, but there > seems to be quite a bit of overlap as well. For example, I would naively > expect asan_interface_test.cc to not require instrumentation -- it almost > exclusively directly calls the runtime. But it is currently being compiled >...

..."ecx", "memory"); \ + : "memory"); \ } } // End of anonymous namespace The error before this change: Current problem with the build after patch: [100%] Generating ASAN_NOINST_TEST_OBJECTS.asan_noinst_test.cc.x86_64-with-calls.o /home/mzuckerm/llvm23/llvm/projects/compiler-rt/lib/asan/tests/asan_asm_test.cc:70:1: error: asm-specifier for input or output variable conflicts with asm clobber list DECLARE_ASM_REP_MOVS(U8, "movsq"); ^ /home/mzuckerm/llvm23/llvm/pro...

...ery firm separation >> between bucket #1 and bucket #2. >> > > (answering parts at a time) > Agree. I am going to fix that now. > This part is fixed by r159135. thanks!! --kcc > > >> Currently, there is one collection of tests clearly in bucket #1 >> (asan_noinst_test.cc), and plenty of tests clearly in bucket #2, but there >> seems to be quite a bit of overlap as well. For example, I would naively >> expect asan_interface_test.cc to not require instrumentation -- it almost >> exclusively directly calls the runtime. But it is currently being co...