public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/16159] malloc_printerr() deadlock, when calling malloc_printerr() again
Date: Thu, 14 Nov 2013 14:32:00 -0000	[thread overview]
Message-ID: <bug-16159-131-aQnjR2omjw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16159-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16159

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |neleai at seznam dot cz

--- Comment #17 from Ondrej Bilka <neleai at seznam dot cz> ---
Joseph, do you have a benchmark to measure libgcc overhead?

I tried a following

cat "int main()
{
  return 42;
}" > x.c
gcc x.c -O3  -o nogcc
gcc x.c -O3 -lgcc -o withgcc
time for I in `seq 1 10000`; do ./nogcc; done
time for I in `seq 1 10000`; do ./withgcc; done

And I cannot distinguish these from noise. When I linked with -lpthread there
was a noticable slowdown.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13  3:30 [Bug malloc/16159] New: " darryl.miles at darrylmiles dot org
2013-11-13  3:31 ` [Bug malloc/16159] " darryl.miles at darrylmiles dot org
2013-11-13  3:37 ` darryl.miles at darrylmiles dot org
2013-11-13  3:44 ` carlos at redhat dot com
2013-11-13  3:57 ` carlos at redhat dot com
2013-11-13  7:57   ` Ondřej Bílka
2013-11-13  7:57 ` neleai at seznam dot cz
2013-11-13 13:00 ` darryl.miles at darrylmiles dot org
2013-11-13 14:31   ` Ondřej Bílka
2013-11-13 13:11 ` darryl.miles at darrylmiles dot org
2013-11-13 14:31 ` neleai at seznam dot cz
2013-11-13 15:50 ` bugdal at aerifal dot cx
2013-11-13 16:03 ` carlos at redhat dot com
2013-11-13 16:12 ` joseph at codesourcery dot com
2013-11-13 16:23   ` Ondřej Bílka
2013-11-13 16:23 ` neleai at seznam dot cz
2013-11-13 16:28 ` bugdal at aerifal dot cx
2013-11-13 16:30 ` bugdal at aerifal dot cx
2013-11-13 16:47 ` joseph at codesourcery dot com
2013-11-13 16:54 ` joseph at codesourcery dot com
2013-11-14 14:32 ` neleai at seznam dot cz [this message]
2013-11-14 15:54 ` bugdal at aerifal dot cx
2013-11-14 16:47 ` neleai at seznam dot cz
2013-11-14 17:08 ` bugdal at aerifal dot cx
2013-11-28 13:52 ` eblake at redhat dot com
2014-02-23 23:34 ` adconrad at 0c3 dot net
2014-06-13 12:18 ` fweimer at redhat dot com
2015-05-19  1:15 ` cvs-commit at gcc dot gnu.org
2015-05-19  1:16 ` siddhesh at redhat dot com

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-16159-131-aQnjR2omjw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).