public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: Terminally slow (75 seconds) on some steps
Date: Mon, 18 Aug 2003 16:15:00 -0000	[thread overview]
Message-ID: <3476CD7A-D197-11D7-B29B-000A95A34564@dberlin.org> (raw)
In-Reply-To: <3F40EB16.5000500@redhat.com>


On Monday, August 18, 2003, at 11:04 AM, Andrew Cagney wrote:

>> First of all, we should be using mmap to access symbol files, at least
>>> when there are no relocations.
>> Been there, done that, was told to do it in BFD.
>
> If there are I/O performances gains to be had, GDB should share them 
> with binutils.
Except, you can't.
Even if we were to use the bfd window stuff, binutils wouldn't be using 
it.
So i'm not sure what you mean.
Whether we directly call mmap, or attempt to use the window stuff 
(which is harder to use for us, and not built to do what we want), 
we're still going to be not sharing it with binutils.
IMHO, it makes more sense to add the 3 lines of code necessary to use 
mmap (we need not change anything else, since bfd reads on the mmap'd 
memory will be turned into memory reads as approriate), than to change 
more to use the window stuff.
> Did you look at bfdwin.c (although, in light of recent patches to 
> modify bfd so that it can create things from target memory, the 
> interface may be heading for review).
>
The mmap usage in it not enabled unless you specifically configure it 
on, last i looked.
In fact, last i looked, the window stuff wasn't even turned on unless 
you used --with-mmap.
This may have changed though.
> Andrew
>
>

  reply	other threads:[~2003-08-18 16:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1057999221.6815.ezmlm@sources.redhat.com>
2003-07-12  9:03 ` Robert Vazan
2003-07-17 16:34   ` Andrew Cagney
2003-07-18 13:06     ` Robert Vazan
2003-07-18 21:56       ` Andrew Cagney
2003-07-19 11:29         ` Robert Vazan
2003-07-21 14:21           ` Andrew Cagney
2003-07-21 17:38             ` Robert Vazan
2003-08-05  5:20               ` Andrew Cagney
2003-08-05 18:04                 ` Robert Vazan
2003-08-05 18:35                   ` Andrew Cagney
2003-08-14 12:05                     ` Robert Vazan
2003-08-15 22:59                       ` Andrew Cagney
2003-08-16 15:11                         ` Daniel Jacobowitz
2003-08-16 16:36                           ` Andrew Cagney
2003-08-16 16:41                             ` Daniel Jacobowitz
2003-08-17  3:29                               ` Daniel Berlin
2003-08-18 15:05                                 ` Andrew Cagney
2003-08-18 16:15                                   ` Daniel Berlin [this message]
2003-08-16 16:38                         ` Robert Vazan
2003-08-20 16:12                         ` Robert Vazan

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=3476CD7A-D197-11D7-B29B-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).