public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55354] [asan] by default, the asan run-time should be linked statically, not dynamically Date: Mon, 19 Nov 2012 08:55:00 -0000 [thread overview] Message-ID: <bug-55354-4-Evrm28ASzg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55354-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-19 08:54:47 UTC --- I bet 9.5% or more of that is due to the PLT call. The thing is, even when you have initial-exec TLS model code, if you link it into an executable and the referenced TLS variable is in the executable, the linker TLS transitions optimization changes the IE model into LE model, so instead of something like: mov 0x2009a9(%rip),%rax mov %fs:(%rax),%eax you'll end up with mov $-4,%rax mov %fs:(%rax),%eax or so (compared to mov %fs:-4,%eax if it was local-exec model from the beginning). Given the amount of code in __tsan_read8, I seriously doubt it is noticeable. So, please compare libtsan built with -fPIC -ftls-model=initial-exec with libtsan built with -fPIE (-ftls-model=local-exec). The former will not require any special hacks and will work just fine even with shared libraries, the latter won't.
next prev parent reply other threads:[~2012-11-19 8:55 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-16 17:03 [Bug other/55354] New: " konstantin.s.serebryany at gmail dot com 2012-11-16 17:15 ` [Bug other/55354] " pinskia at gcc dot gnu.org 2012-11-16 17:21 ` dvyukov at google dot com 2012-11-16 17:22 ` jakub at gcc dot gnu.org 2012-11-16 20:28 ` konstantin.s.serebryany at gmail dot com 2012-11-16 20:47 ` jakub at gcc dot gnu.org 2012-11-16 20:54 ` konstantin.s.serebryany at gmail dot com 2012-11-17 20:36 ` hjl.tools at gmail dot com 2012-11-17 21:08 ` markus at trippelsdorf dot de 2012-11-18 19:36 ` konstantin.s.serebryany at gmail dot com 2012-11-18 19:54 ` jakub at gcc dot gnu.org 2012-11-18 19:59 ` konstantin.s.serebryany at gmail dot com 2012-11-18 20:10 ` jakub at gcc dot gnu.org 2012-11-19 4:13 ` konstantin.s.serebryany at gmail dot com 2012-11-19 8:55 ` jakub at gcc dot gnu.org [this message] 2012-11-19 9:03 ` konstantin.s.serebryany at gmail dot com 2012-11-19 9:06 ` konstantin.s.serebryany at gmail dot com 2012-11-19 10:53 ` dvyukov at google dot com 2012-11-21 7:45 ` dvyukov at google dot com 2012-11-21 8:43 ` jakub at gcc dot gnu.org 2012-11-21 9:06 ` dvyukov at google dot com 2012-11-21 9:26 ` jakub at gcc dot gnu.org 2012-11-23 7:17 ` [Bug sanitizer/55354] " dvyukov at google dot com 2012-11-23 7:28 ` dvyukov at google dot com 2012-11-23 8:14 ` jakub at gcc dot gnu.org 2012-11-23 8:22 ` jakub at gcc dot gnu.org 2012-11-23 8:36 ` dvyukov at google dot com 2012-11-23 10:47 ` konstantin.s.serebryany at gmail dot com 2012-11-23 11:16 ` konstantin.s.serebryany at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-55354-4-Evrm28ASzg@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).