public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "konstantin.s.serebryany at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55354] [asan] by default, the asan run-time should be linked statically, not dynamically
Date: Fri, 23 Nov 2012 11:16:00 -0000 [thread overview]
Message-ID: <bug-55354-4-l1rHUoIlYB@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 #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.
/usr/bin/ld: .libs/tsan_rtl_thread.o: relocation R_X86_64_PC32 against
undefined symbol `__tsan_trace_switch_thunk' can not be used when making a
shared objec
Apparently, Wei hacked this around by enabling pure-C++ code, which is slower.
prev parent reply other threads:[~2012-11-23 11:16 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
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 [this message]
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-l1rHUoIlYB@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: link
Be 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).