Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Kevin Buettner <kevinb@cygnus.com>, gdb@sources.redhat.com
Subject: Re: gdb and dlopen
Date: Wed, 17 Oct 2001 17:05:00 -0000	[thread overview]
Message-ID: <20011017200554.A28537@nevyn.them.org> (raw)
In-Reply-To: <3BCE0CA6.3040302@cygnus.com>

On Wed, Oct 17, 2001 at 06:56:38PM -0400, Andrew Cagney wrote:
> >On Oct 17,  1:19am, Daniel Jacobowitz wrote:
> >
> >
> >>Amusingly, there are something like eight million calls to
> >>ptid_get_pid.  I'll send along a trivial patch to shrink the worst
> >>offenders.  I understand the opacity that functions over macros is
> >>going for here, but a function that does 'return a.b;' and gets called
> >>eight MILLION times is a little bit absurd, don't you think?  Absurd
> >>enough that it shows up as the second highest item on the profile.
> >
> >
> >It's a shame that we can't use inline functions...
> 
> Remember, ptid_get_pid() is the messenger.  The real problem is 
> elsewhere.  A bit like STREQ() in the symtab code.

I don't understand what you mean by this.  We certainly need to get at
the actual PID everywhere PIDGET () is being used, regardless of
whether it could be hoisted out of loops.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-10-17 17:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <y3radyrjqf8.wl@paladin.sgrail.com>
2001-10-16 13:15 ` Daniel Jacobowitz
2001-10-16 18:23   ` Kimball Thurston
     [not found]     ` <20011016213252.A8694@nevyn.them.org>
2001-10-16 19:03       ` Daniel Jacobowitz
2001-10-16 20:04         ` Kimball Thurston
2001-10-16 20:17           ` Andrew Cagney
2001-10-16 22:08             ` Daniel Jacobowitz
2001-10-16 22:19               ` Daniel Jacobowitz
     [not found]                 ` <y3rzo6qx1ej.wl@paladin.sgrail.com>
2001-10-16 22:52                   ` Kimball Thurston
2001-10-17  8:07                 ` Mark Kettenis
2001-10-17  8:29                   ` H . J . Lu
2001-10-17 11:09                   ` Daniel Jacobowitz
2001-10-17 14:26                     ` Mark Kettenis
2001-10-17 14:34                       ` Daniel Jacobowitz
2001-10-17  8:54                 ` Andrew Cagney
2001-10-17 15:08                 ` Kevin Buettner
2001-10-17 15:57                   ` Andrew Cagney
2001-10-17 17:05                     ` Daniel Jacobowitz [this message]
2001-10-17 23:14                       ` Andrew Cagney
2001-10-17  8:42               ` Andrew Cagney
2001-10-17 11:15                 ` Daniel Jacobowitz
2001-10-17 12:09                   ` Kimball Thurston
2001-10-17 12:58                     ` Kevin Buettner
2001-11-08  0:22                       ` Daniel Jacobowitz
2001-11-08  8:17                         ` Kevin Buettner
2001-11-08  9:44                           ` Daniel Jacobowitz
2001-11-08 10:49                             ` Kevin Buettner
2001-11-08 11:14                               ` Daniel Jacobowitz
2001-11-08 16:17                                 ` Andrew Cagney
2001-10-16 22:25             ` Kimball Thurston
2001-10-16 15:05 ` H . J . Lu

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=20011017200554.A28537@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@cygnus.com \
    /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