[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-23 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #24 from Jakub Jelinek jakub at gcc dot gnu.org 2012-11-23 08:13:11 UTC --- When I rebuild libtsan with -fPIE instead of -fPIC in the Makefile, and g++ -shared -Wl,--whole-archive -o libtsanx.so libtsan.a -ldl -lpthread (note

[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-23 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #25 from Jakub Jelinek jakub at gcc dot gnu.org 2012-11-23 08:20:40 UTC --- Have you considered using __builtin_expect to help the compiler in the performance sensitive code? Or even better would be profile-feedback, build

[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-23 Thread dvyukov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #26 from Dmitry Vyukov dvyukov at google dot com 2012-11-23 08:34:52 UTC --- (In reply to comment #25) Have you considered using __builtin_expect to help the compiler in the performance sensitive code? Or even better would

[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-23 Thread konstantin.s.serebryany at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #27 from Konstantin Serebryany konstantin.s.serebryany at gmail dot com 2012-11-23 10:47:14 UTC --- is it really so crucial that you'd want to make another libtsan_pie.a for it? I would actually prefer to have *only*

[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-23 Thread konstantin.s.serebryany at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #28 from Konstantin Serebryany konstantin.s.serebryany at gmail dot com 2012-11-23 11:14:58 UTC --- Note that today's upstream tsan sources don't link with -fPIC at all because our assembly blobs are not PIC-friendly.

[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-22 Thread dvyukov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #22 from Dmitry Vyukov dvyukov at google dot com 2012-11-23 07:16:14 UTC --- For dynamic libraries that are loaded into a non-instrumented executable (e.g. swig so preloaded into python process), we statically link the

[Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically

2012-11-22 Thread dvyukov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #23 from Dmitry Vyukov dvyukov at google dot com 2012-11-23 07:27:27 UTC --- (In reply to comment #21) (In reply to comment #20) What I see is that it also affect code generation (register allocation). Do we need to