search for: mvma

...a global value. Instrument each function to load that value into a local register. Instrument each load/store/malloc/free to check the VMA based on that register. This may be optimised by the compiler for the compiler instrumented code, but will not for the library calls. 2. Add a compiler option -mvma=NN that chooses at compile time the VMA and makes it static in the user code. This has the same performance as currently for compiler instrumented code, but will not be for library calls, especially for the dynamic version. This is faster, but it's also less flexible than option 1, though more...

...ush it up to 56 bits in the near future. So, there are only three paths we can take: 1. Keep it constant, today at 42, and increase the constant slowly, as kernels start popping in with higher VMAs. This could slow down for large values of VMA and low values on kernel. 2. Create a compiler flag -mvma=NN. This would be as fast as native when chosen correctly, but could break if lower than the machine's VMA. 3. Make it dynamic, so that the VMA value doesn't matter. I really have no idea on what the impact of dynamic VMA will have on the sanitizers, nor I have on what it would be if we c...

Jakub makes a good point, are you sure that there is no single shadow offset value that works for all VMA variants? What exactly breaks when 1<<36 is used on 42-bit VMA? On Fri, Sep 25, 2015 at 3:28 AM, Yury Gribov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 09/25/2015 01:27 PM, Yury Gribov wrote: >> >> On 09/25/2015 11:53 AM, Jakub Jelinek via llvm-dev