Displaying 3 results from an estimated 3 matches for "__asan_report_load8".
2014 Nov 02
2
[LLVMdev] So I just did a normal 'ninja check' with a CMake build that enables ASan and the go bindings tests are... busted...
Specifically, the test is causing a link to occur for CGO stuff. It has
been running 8 minutes now with Gold, and is producing a 400mb .o file
afaict:
% du -hs /tmp/go-build703430446/
llvm.org/llvm/bindings/go/llvm/_test/_obj_test/_cgo_.o
397M /tmp/go-build703430446/
llvm.org/llvm/bindings/go/llvm/_test/_obj_test/_cgo_.o
What am I doing wrong here?
-------------- next part --------------
An
2016 Oct 26
2
Asan code size overhead
Hi Kcc,
I'm trying enabling the Asan in my firmware, but I find the asan instrumentation code size impact is too big for me. I just implement necessary firmware version runtime library functions (e.g. __asan_report_load8) with blank body firstly to pass the asan enabled build, but I find the new binary code size is already ~2.5 times as original one with asan disabled in GCC. I know Linux kernel already enabled the asan (a.k.a Kasan), and is there any magic of asan for Linux to control its code size impact? Please...
2016 Oct 26
0
Asan code size overhead
...2016 at 7:42 AM, Shi, Steven <steven.shi at intel.com> wrote:
> Hi Kcc,
>
> I’m trying enabling the Asan in my firmware, but I find the asan
> instrumentation code size impact is too big for me. I just implement
> necessary firmware version runtime library functions (e.g.
> __asan_report_load8) with blank body firstly to pass the asan enabled
> build, but I find the new binary code size is already ~2.5 times as
> original one with asan disabled in GCC. I know Linux kernel already enabled
> the asan (a.k.a Kasan), and is there any magic of asan for Linux to control
> its code...