public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: hjl@nynexst.com
Cc: gas2@cygnus.com, eric@aib.com
Subject: Re: Add -N support to ELF?
Date: Mon, 20 Feb 1995 14:03:00 -0000	[thread overview]
Message-ID: <9502202203.AA27479@tweedledumb.cygnus.com> (raw)
In-Reply-To: <9502202113.AA25517@titanic.nynexst.com>

   From: hjl@nynexst.com (H.J. Lu)
   Date: Mon, 20 Feb 95 16:18:38 EST

   This patch is derived from some patch I got, Eric? It should work
   fine. Ian, is that ok to uncomment my patch to elf.sc with this one
   applied? I guess the docs should be updated to reflect the usage
   of -N in ELF.

The basic problem with this approach is that I believe it will cause
the linker to unexpectedly abort if, say, one of the input files has a
writable .text section.  Try it.

The linker already aborts unexpectedly far too often, and I would
prefer not to introduce another possibility.  If you can write the
patch in such a fashion that it can not cause a linker abort--perhaps
by making it retry the division of sections into segments if the first
attempt uses too many segments--I would be more willing to put this
in.  The beneficial effects of this patch are vanishingly small--it
saves one page of virtual memory address space (not virtual memory
itself, but just the address space) for a very small number of
programs--so IMHO it should only be put in if it is completely safe.

Ian


  reply	other threads:[~1995-02-20 14:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-02-20  8:04 More gas/bfd patches Bryan Ford
1995-02-20  8:18 ` Ian Lance Taylor
1995-02-20 10:32   ` Add -N support to ELF? H.J. Lu
1995-02-20 11:29     ` Ian Lance Taylor
1995-02-20 12:50       ` H.J. Lu
1995-02-20 13:20       ` H.J. Lu
1995-02-20 14:03         ` Ian Lance Taylor [this message]
1995-02-20 14:44           ` H.J. Lu
1995-02-20 15:48             ` Ian Lance Taylor

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=9502202203.AA27479@tweedledumb.cygnus.com \
    --to=ian@cygnus.com \
    --cc=eric@aib.com \
    --cc=gas2@cygnus.com \
    --cc=hjl@nynexst.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).