public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59061] Port leaksanitizer
Date: Thu, 14 Nov 2013 15:01:00 -0000	[thread overview]
Message-ID: <bug-59061-4-KgzM5xYFDk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59061-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #19 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Kostya Serebryany from comment #18)
> I don't think we've measured pure-lsan slowdown, but I expect it to be small.
> asan/lsan bring in a different allocator (malloc/free).
> We tried to make it very fast and our measurements show that's it is close
> to 
> tcmalloc performance (but a bit more greedy in memory).
> It also performs stack unwind on every malloc, so on malloc-intensive apps
> you may see some small slowdown.

I our simulation code, it looks like the overhead for leak checking is about
20%. I haven't done very careful measurements yet, since this is more or less
what we're willing to pay to integrate the (very useful) feature in our testing
setup.


  parent reply	other threads:[~2013-11-14 15:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  9:57 [Bug sanitizer/59061] New: " Joost.VandeVondele at mat dot ethz.ch
2013-11-09  9:58 ` [Bug sanitizer/59061] " Joost.VandeVondele at mat dot ethz.ch
2013-11-09 16:02 ` kcc at gcc dot gnu.org
2013-11-09 16:13 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-09 16:14 ` kcc at gcc dot gnu.org
2013-11-09 16:28 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-10  2:27 ` kcc at gcc dot gnu.org
2013-11-10  6:32 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-14  9:40 ` kcc at gcc dot gnu.org
2013-11-14  9:51 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-14  9:58 ` kcc at gcc dot gnu.org
2013-11-14  9:59 ` jakub at gcc dot gnu.org
2013-11-14 10:06 ` kcc at gcc dot gnu.org
2013-11-14 10:09 ` jakub at gcc dot gnu.org
2013-11-14 10:41 ` kcc at gcc dot gnu.org
2013-11-14 11:08 ` samsonov at google dot com
2013-11-14 14:02 ` pinskia at gcc dot gnu.org
2013-11-14 14:20 ` earthdok at google dot com
2013-11-14 14:28 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-14 14:52 ` kcc at gcc dot gnu.org
2013-11-14 15:01 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2013-11-14 15:05 ` kcc at gcc dot gnu.org
2013-11-14 15:10 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-14 15:27 ` kcc at gcc dot gnu.org
2013-11-14 17:18 ` jakub at gcc dot gnu.org
2013-11-15 16:25 ` jakub at gcc dot gnu.org
2013-11-15 17:48 ` kcc at gcc dot gnu.org
2013-11-15 22:18 ` jakub at gcc dot gnu.org
2013-11-17 10:35 ` samsonov at google dot com
2013-11-22 21:13 ` jakub at gcc dot gnu.org
2013-11-23  9:21 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-23 11:17 ` kcc at gcc dot gnu.org
2013-11-23 12:58 ` kcc at gcc dot gnu.org
2013-11-23 13:50 ` earthdok at google dot com
2013-11-23 14:02 ` jakub at gcc dot gnu.org
2013-11-23 16:11 ` kcc at gcc dot gnu.org
2013-11-24 14:41 ` earthdok at google dot com
2013-11-25 14:50 ` earthdok at google dot com
2013-12-06  6:50 ` Joost.VandeVondele at mat dot ethz.ch
2013-12-06  7:19 ` kcc at gcc dot gnu.org
2013-12-06  8:16 ` Joost.VandeVondele at mat dot ethz.ch
2014-01-10  7:20 ` Joost.VandeVondele at mat dot ethz.ch

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-59061-4-KgzM5xYFDk@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).