From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4260 invoked by alias); 22 Feb 2013 07:11:47 -0000 Received: (qmail 4154 invoked by uid 48); 22 Feb 2013 07:11:15 -0000 From: "kcc at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/55309] gcc's address-sanitizer 66% slower than clang's Date: Fri, 22 Feb 2013 07:11: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: enhancement X-Bugzilla-Who: kcc at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 2013-02/txt/msg02205.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55309 --- Comment #43 from Kostya Serebryany 2013-02-22 07:11:06 UTC --- gcc r196201: -O2 -fno-aggressive-loop-optimizations clang 175735: -O2 x86_64 linux, both are using the new 7fff8000 shadow offset 400.perlbench, 1136.00, -1.00, -0.00 401.bzip2, 838.00, 1154.00, 1.38 403.gcc, 716.00, 742.00, 1.04 429.mcf, 582.00, 578.00, 0.99 445.gobmk, 801.00, 1138.00, 1.42 456.hmmer, 1277.00, 1515.00, 1.19 458.sjeng, 869.00, 1258.00, 1.45 462.libquantum, 532.00, 469.00, 0.88 464.h264ref, 1303.00, 4395.00, 3.37 471.omnetpp, 568.00, 585.00, 1.03 473.astar, 647.00, 748.00, 1.16 483.xalancbmk, 460.00, 534.00, 1.16 433.milc, 659.00, 614.00, 0.93 444.namd, 592.00, 531.00, 0.90 447.dealII, 614.00, 706.00, 1.15 450.soplex, 367.00, 406.00, 1.11 453.povray, 423.00, 410.00, 0.97 470.lbm, 377.00, 401.00, 1.06 482.sphinx3, 958.00, 1325.00, 1.38 400.perlbench fails with a global-buffer-overflow which clang does not detect. I did not investigate why. It could be a gcc false positive or clang false negative. 464.h264ref is VERY slow, I did not look why.