From: Grant Grundler <grundler@parisc-linux.org>
To: linux-ia64@vger.kernel.org
Subject: [carlos@baldric.uwo.ca: Good news for glibc.]
Date: Mon, 05 Jan 2004 18:33:49 +0000 [thread overview]
Message-ID: <20040105183349.GC9004@colo.lackof.org> (raw)
glibc profiling?
This was originally posted on debian-hppa/parisc-linux mailing lists.
grant
----- Forwarded message from Carlos O'Donell <carlos@baldric.uwo.ca> -----
Old-Return-Path: <carlos@baldric.uwo.ca>
X-Original-To: debian-hppa@lists.debian.org
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org,
debian-hppa@lists.debian.org, lamont@debian.org
Subject: Good news for glibc.
X-Useless-Header: listen, love, accept, mindfullness, patience, and humility.
Resent-Message-ID: <AW1MyC.A.LG.3eQ-_@murphy>
Resent-From: debian-hppa@lists.debian.org
X-Mailing-List: <debian-hppa@lists.debian.org> archive/latest/3162
List-Id: <debian-hppa.lists.debian.org>
List-Post: <mailto:debian-hppa@lists.debian.org>
List-Help: <mailto:debian-hppa-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-hppa-request@lists.debian.org?subject=subscribe>
List-Unsubscribe: <mailto:debian-hppa-request@lists.debian.org?subject=unsubscribe>
List-Archive: <http://lists.debian.org/debian-hppa/>
Resent-Sender: debian-hppa-request@lists.debian.org
Resent-Date: Mon, 5 Jan 2004 00:44:07 -0600 (CST)
X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at lackof.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
colo.lackof.org
X-Spam-Status: No, hits=-4.9 required=5.0 testsºYES_00 autolearn=ham
version=2.60
X-Spam-Level:
On Thu, Jan 01, 2004 at 04:00:16PM -0500, John David Anglin wrote:
> > The main issue was that the 'start' symbol needs to be canonicalized
> > before passing on to the gmon routines. This requires entry.h to be
>
> I still think that using __c_f_f_c for this special case is overkill.
What could we use?
Good news, I just fixed LD_PROFILE so I can actually check to see what
functions take up too much time :) I think I inadvertently fixed it for
ia64 too... what do ia64 people use to profile glibc?
c.
A tempting peek! :)
% cumulative self self total
time seconds seconds calls us/call us/call name
0.00 0.00 0.00 14000 0.00 cfree
0.00 0.00 0.00 6000 0.00 memset
0.00 0.00 0.00 2004 0.00 malloc
0.00 0.00 0.00 2003 0.00 flockfile
0.00 0.00 0.00 2003 0.00 funlockfile
0.00 0.00 0.00 2001 0.00 __cxa_finalize
0.00 0.00 0.00 1002 0.00 index
0.00 0.00 0.00 1000 0.00 __GI__dl_close
0.00 0.00 0.00 1000 0.00 __GI__dl_open
0.00 0.00 0.00 1000 0.00 printf
0.00 0.00 0.00 1000 0.00 puts
0.00 0.00 0.00 1000 0.00 strlen
0.00 0.00 0.00 1 0.00 __libc_start_main
0.00 0.00 0.00 1 0.00 realloc
0.00 0.00 0.00 1 0.00 strrchr
--
To UNSUBSCRIBE, email to debian-hppa-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
----- End forwarded message -----
next reply other threads:[~2004-01-05 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 18:33 Grant Grundler [this message]
2004-01-05 19:06 ` [carlos@baldric.uwo.ca: Good news for glibc.] David Mosberger
2004-01-05 19:31 ` Carlos O'Donell
2004-01-05 22:07 ` David Mosberger
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=20040105183349.GC9004@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-ia64@vger.kernel.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