public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: jtc@redback.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: linker memory footprint
Date: Mon, 04 Oct 1999 18:32:00 -0000	[thread overview]
Message-ID: <19991005013145.18030.qmail@daffy.airs.com> (raw)
In-Reply-To: <5miu4m7gf8.fsf@jtc.redbacknetworks.com>

   From: jtc@redback.com (J.T. Conklin)
   Date: 04 Oct 1999 18:19:23 -0700

   Before sending the IT group out to buy SIMMs, I'm wondering if there
   are any changes we can make to either the way our image is linked or a
   linker memory reduction project I can sell management that I should be
   working on.

Are you using the --no-keep-memory option?

   Short a project that keeps debug information in the object files and
   modifies GDB to find it there, is there anything that can be done to
   reduce ld's memory usage?

It would be possible to reduce ELF memory usage somewhat, and speed it
up somewhat, by adding an option to skip checking the relocations in
the first pass.  This would only be correct when not doing dynamic
linking, so it could not be the default.  Also, the --no-keep-memory
option would cause about the same amount of memory savings anyhow.

I don't know of any way to reduce memory usage of the a.out linker.

It's quite possible that there is some way to reduce memory usage, but
I just haven't thought of it.  It's also quite possible that there are
bugs.  I don't want to discourage you from investigating.

Ian

  reply	other threads:[~1999-10-04 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04 18:20 J.T. Conklin
1999-10-04 18:32 ` Ian Lance Taylor [this message]
1999-10-05  9:32   ` hppa1.1-rtems grepossible failure ?\x03 Joel Sherrill
1999-10-06  7:30     ` hppa1.1-rtems grepossible failure ? Jeffrey A Law
1999-10-06  9:38       ` Joel Sherrill

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=19991005013145.18030.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).