search for: bitvector_any1

...l hundred time - I suspect the issue is with MCJIT having to process a ton more relocations and code and being inefficient at it, but I can't prove that). That's not the issue however. Eventually, I get ==17150== WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x7f417cea3189 in bitvector_any1 /home/kfischer/julia-san/src/support/bitvector.c:177 [ snip ] Uninitialized value was created by a heap allocation #0 0x7f41815de543 in __interceptor_malloc /home/kfischer/julia-san/deps/llvm-svn/projects/compiler-rt/lib/msan/msan_interceptors.cc:854 #1 0x7f417cc7d7f1 in alloc_big /home/...

...MCJIT having to process a ton more relocations >> and code and being inefficient at it, but I can't prove that). That's not >> the issue however. Eventually, I get >> >> ==17150== WARNING: MemorySanitizer: use-of-uninitialized-value >> #0 0x7f417cea3189 in bitvector_any1 >> /home/kfischer/julia-san/src/support/bitvector.c:177 >> [ snip ] >> >> Uninitialized value was created by a heap allocation >> #0 0x7f41815de543 in __interceptor_malloc >> /home/kfischer/julia-san/deps/llvm-svn/projects/compiler-rt/lib/msan/msan_intercep...

...t; >> and code and being inefficient at it, but I can't prove that). That's >> not >> >> the issue however. Eventually, I get >> >> >> >> ==17150== WARNING: MemorySanitizer: use-of-uninitialized-value >> >> #0 0x7f417cea3189 in bitvector_any1 >> >> /home/kfischer/julia-san/src/support/bitvector.c:177 >> >> [ snip ] >> >> >> >> Uninitialized value was created by a heap allocation >> >> #0 0x7f41815de543 in __interceptor_malloc >> >> >> /home/kfischer/juli...

...Shadow for b should be passed at offset 0 in __msan_param_tls. MSan could propagate shadow through arithmetic and even some logic operations (like select). It could be that b is clean on function entry, but then something uninitialized gets mixed in. Also, what is this @entry stuff? It looks like bitvector_any1 has 6 arguments, but your ccall snippet only sets up tls for 3. On Sun, Feb 2, 2014 at 10:39 PM, Keno Fischer <kfischer at college.harvard.edu> wrote: > I don't think we're doing anything unusual. Here's the relevant snippet from > the generated IR for ccall (after instrum...

...but I can't prove that). That's >>>> >> not >>>> >> the issue however. Eventually, I get >>>> >> >>>> >> ==17150== WARNING: MemorySanitizer: use-of-uninitialized-value >>>> >> #0 0x7f417cea3189 in bitvector_any1 >>>> >> /home/kfischer/julia-san/src/support/bitvector.c:177 >>>> >> [ snip ] >>>> >> >>>> >> Uninitialized value was created by a heap allocation >>>> >> #0 0x7f41815de543 in __interceptor_malloc >&g...

...param_tls. >> >> MSan could propagate shadow through arithmetic and even some logic >> operations (like select). It could be that b is clean on function >> entry, but then something uninitialized gets mixed in. >> >> Also, what is this @entry stuff? It looks like bitvector_any1 has 6 >> arguments, but your ccall snippet only sets up tls for 3. >> >> >> On Sun, Feb 2, 2014 at 10:39 PM, Keno Fischer >> <kfischer at college.harvard.edu> wrote: >> > I don't think we're doing anything unusual. Here's the relevant snippet...

...uld propagate shadow through arithmetic and even some logic > >>> operations (like select). It could be that b is clean on function > >>> entry, but then something uninitialized gets mixed in. > >>> > >>> Also, what is this @entry stuff? It looks like bitvector_any1 has 6 > >>> arguments, but your ccall snippet only sets up tls for 3. > >>> > >>> > >>> On Sun, Feb 2, 2014 at 10:39 PM, Keno Fischer > >>> <kfischer at college.harvard.edu> wrote: > >>> > I don't think we're d...