Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: ian@zembu.com
Cc: dan@cgsoftware.com, jhaller@lucent.com, jtc@redback.com,
	cgf@redhat.com, gdb@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: stabs vs. dwarf-2 for C programs
Date: Fri, 13 Apr 2001 22:37:00 -0000	[thread overview]
Message-ID: <200104140537.BAA20048@envy.delorie.com> (raw)
In-Reply-To: <sisnjcrrbi.fsf@daffy.airs.com>

> > I'm pretty sure this alone will cut linking time by a large factor,
> > based on the number of seeks and the amount of time they are taking,
> > in a few tests i just did.
> 
> It's possible.  Around 1997 or so I tried using mmap as you suggest.
> It actually made the linker slower on the systems I tested it on,
> including Solaris and on the Linux kernel, so I dropped the effort.
> But, as you say, times change, and maybe now it would indeed be
> faster.  It's an easy optimization in BFD; why don't you try it?

One of the optimizations in DJGPP's runtime library is specifically
because the linker does a lot of seeks (other programs, like gcc, tend
to stream data instead).  We changed the buffer size dynamically to
adapt to random vs linear accesses.  Of course, this assumes your
default buffer size is bigger than a sector anyway.  Linux seems to
have a 4k buffer; try setting the buffer size to 512 for all bfds in
the linker and see if it improves performance.


  reply	other threads:[~2001-04-13 22:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 19:13 J.T. Conklin
2001-04-12 19:17 ` Christopher Faylor
2001-04-12 19:31   ` J.T. Conklin
2001-04-12 19:59     ` Daniel Berlin
2001-04-13  7:13       ` John Haller
2001-04-13  8:09         ` Daniel Berlin
2001-04-13 16:18           ` Ian Lance Taylor
2001-04-13 18:39             ` Daniel Berlin
2001-04-13 20:22               ` Ian Lance Taylor
2001-04-13 22:01                 ` Daniel Berlin
2001-04-13 22:19                   ` Ian Lance Taylor
2001-04-13 22:37                     ` DJ Delorie [this message]
2001-04-13 23:31                     ` Daniel Berlin
2001-04-13 23:47                       ` Daniel Berlin
2001-04-13 23:51                       ` Ian Lance Taylor
2001-04-13 22:56                   ` Daniel Berlin
2001-04-13 23:40                     ` Ian Lance Taylor
2001-04-13 23:55                   ` Todd Whitesel
2001-04-12 19:55 ` Daniel Berlin
2001-04-12 23:37   ` Eli Zaretskii
2001-04-13  8:13     ` Daniel Berlin
2001-04-12 22:00 ` Geoff Keating
2001-04-12 22:37   ` Daniel Berlin

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=200104140537.BAA20048@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgf@redhat.com \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sources.redhat.com \
    --cc=ian@zembu.com \
    --cc=jhaller@lucent.com \
    --cc=jtc@redback.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