search for: lasan

...stalled toolchains, >>> and even GCC. >>> >>> Sounds good. >>> >>> >>> > Clang driver links the static xsan runtimes from a hardcoded >>> > paths in Clang resource directory, and doesn't add flags like >>> > "-lasan -L/path/to/clang/resource/dir". I find this behavior >>> reasonable. >>> >>> Can we change the flags to "-lasan -L/path/to/clang/resource/dir"? If >>> we make that change, >> >> >> I don't think it's a good idea to let us...

...;wins" over -L/path/to/clang/resource/dir, and we have strong >> reasons to put the latter as early in the link line as possible. > > Some good news, the drivers (both gcc and clang) allow us to put the > '-L' parameters after the '-l' parameters. So we can put -lasan at > the start of the parameter list to get the desired link order and -L > at the end so that the user-specified runtime is always chosen. > > -Greg > > > On Fri, Apr 4, 2014 at 5:57 AM, Alexey Samsonov <samsonov at google.com> wrote: >> >> On Thu, Apr 3, 201...

...not a library tests. We > need to verify that simple command > "clang -fsanitize=address foo.cc" works, and produce a binary that works as > expected. As an illustration, suppose > the following sequence of events > 1) we land your changes to Clang driver, so that it uses -lasan > -L/path/to/clang/resource/dir > 2) we add additional -L/path/to/compiler-rt/libs to all %clang invocations > in lit test-suite. > 3) someone accidentally breaks the Clang dirver, and now it uses > -L/wrong/path/to/clang/resource/dir > We will not be able to detect this error. Th...

...-rt test-suite in a standalone mode, > to test fully built/installed toolchains, > and even GCC. > > Sounds good. > > > > Clang driver links the static xsan runtimes from a hardcoded > > paths in Clang resource directory, and doesn't add flags like > > "-lasan -L/path/to/clang/resource/dir". I find this behavior reasonable. > > Can we change the flags to "-lasan -L/path/to/clang/resource/dir"? If > we make that change, I don't think it's a good idea to let user hijack the driver and stuff in custom version of ASan runti...

...1) we would still want to use compiler-rt test-suite in a standalone mode, to test fully built/installed toolchains, and even GCC. 2) Adding -L... wouldn't work: Clang driver links the static xsan runtimes from a hardcoded paths in Clang resource directory, and doesn't add flags like "-lasan -L/path/to/clang/resource/dir". I find this behavior reasonable. I don't see a problem with the current approach - we can make "run sanitizer test suite" command in the top-level build tree depend on "build/install compiler-rt ExternalProject" steps (see how it's d...

Kostya Serebryany wrote: > I don't know anything about haskell, but if you post a minimal reproducer > here > we *may* be able to help. Its just so happens that I do have something here: https://github.com/erikd-ambiata/haskell-sanitize The Readme should have all the information you need. Any problems, please let mw know. Cheers, Erik --

It does sound like Android is better suited for "honest" cross-compilation, rather than "build compiler-rt for all targets we can find" model. I'm still not convinced that we must require the "ninja install" step. Could we just "ninja clang" and then build the second stage against the first stage build directory? Will this "find_package" thing