From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4038 invoked by alias); 23 Nov 2012 08:36:26 -0000 Received: (qmail 28608 invoked by uid 48); 23 Nov 2012 08:34:55 -0000 From: "dvyukov at google dot com" 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 08:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer 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: In-Reply-To: References: 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: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg02174.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55354 --- Comment #26 from Dmitry Vyukov 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 be profile-feedback, build > libtsan once, run some benchmark, build libtsan again. There are few of them in the code in the obvious cases. The performance is very shaky and depends on compiler, compiler version and options. I remember I get worse results when I added some other likily/unlikely. I didn't have time for more comprehensive investigation. FDO may be a good idea for prebuild libraries.