<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 31 January 2014 09:59, Alexey Samsonov <span dir="ltr"><<a href="mailto:samsonov@google.com" target="_blank">samsonov@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>Huh? What tests are you talking about? I thought that tests for Clang driver verifiy that the command "clang++ -fsanitize=address ...." produce a correct linker invocation (with path to /lib/clang/3.5/linux/libclang_rt.asan-arm.a), but don't actually require the libraries to be built there. If it's not the case, we should fix that.</div>
</div></div></div></blockquote><div></div></div><br></div><div class="gmail_extra">I got linker errors, since /lib/clang/3.5/linux/libclang_rt.asan-armv7l.a (or arm for that matter) wasn't there, since "arm" is not a recognized architecture.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">My point is that Clang sanitizer tests should *only* run IFF:</div><div class="gmail_extra"><br></div><div class="gmail_extra">1. Compiler-rt is present AND</div>
<div class="gmail_extra">2. The architecture is recognized AND</div><div class="gmail_extra">3. The Asan/Lsan/UBsan etc libraries were enabled via some build option (individually checked).</div><div class="gmail_extra"><br>
</div><div class="gmail_extra">I may be wrong, but right now, it seems that they all run once compiler-rt is available.</div><div class="gmail_extra"><br></div><div class="gmail_extra">cheers,</div><div class="gmail_extra">
--renato</div></div>