From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-407076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 3304 invoked by alias); 19 Nov 2012 10:53:18 -0000
Received: (qmail 3271 invoked by uid 48); 19 Nov 2012 10:53:05 -0000
From: "dvyukov at google dot com" <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 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dvyukov at google dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55354-4-F9phIlsas5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55354-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55354-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-11/txt/msg01738.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354

--- Comment #17 from Dmitry Vyukov <dvyukov at google dot com> 2012-11-19 10:53:04 UTC ---
>When building libtsan as a shared library (for which I had to hack our assembly
>blobs a bit) we get two sources of slowdown: 
>  1. __tsan_read8 and friends are called through PLT
>  2. __tsan_read8 and friends use one extra load to get to TLS

> I bet 9.5% or more of that is due to the PLT call.

That's not the overhead you are looking for, Luke.

We currently compile with -fPIC and link statically, linker inserts only 1
memory dereference in this case. However, -fPIC affects code generation in
compiler, it has to reserve more registers for tls access code and has to
allocate stack frame because of the potential call. Only that causes *20%*
slowdown on a real application (not a synthetic benchmark).

Kostya, to evaluate initial-exec you need to insure that code characteristics
of __tsan_read/write are not affected, i.e. 0 stack spills and analyze script
passes. Everything else we have w/o initial-exec.