similar to: Attempt to modify memory sanitizer for support of X86

It would appear that the fix for https://bugs.llvm.org/show_bug.cgi?id=24155 really only applies to X86. Which I suppose is fine since that's where the bug was reported. However, we've recently upgraded the OS's on some of our PPC64 systems and are hitting the same problems. I certainly wouldn't mind providing a similar fix for PPC, but I don't know what the values in

On Tue, Oct 20, 2015 at 10:53 PM, Kostya Serebryany <kcc at google.com> wrote: > Can you open a separate bug with exact repro instructions? Well the bug tracker seems to require an account. But in any case I don't see anything specific to reproduce. I did an svn update of llvm and clang and built and installed (I even tried make clean and removed the old install but it didn't

RFC: Generalize means the sanitizers work with memory Overview ======== Currently, LLVM sanitizers, such as Asan and Tsan, are tied to a specific memory model that relies on presence of hardware support for virtual memory. This prevents sanitizers from being used on platforms that lack such support, but otherwise are capable of running sanitized programs. Our research indicates that adding

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no

Hi all, I would like to set up an iterative read & write sequence to avoid reading and writing each file one at a time. Hundreds of data sets to re-calculate.? The code I have works well individually, but would like to set up an iterative read, calculate and write changing the input and output file names each iteration. I? think I have read that there is an R? feature using

Hi everyone. Thanks to everyone for taking the time to meet yesterday. I think it was very productive! I am writing to keep a "minutes" of the meet, as I remember them. Action Items: - Jasonk: split up bionic patch to explicitly replace CPP macros with actual calls, one file at a time. - Google/Android: pthread_barrier interface in bionic - *Enh*: 1 paragraph to explain

Hello, normally buffer overflows are detected by address sanitizer. Then I recognized, that this is not the case, if the array is located inside a structure. Thus I created a small example (test.c): struct xxx {    int a;    int buffer[10];    int b; }; int main(void) {    struct xxx var;    int buffer[10];    int count;    for (count = 0; count <=10; count++) {