public inbox for bfd@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: cato@df.lth.se
Cc: bfd@cygnus.com
Subject: Re: a.out questions
Date: Fri, 01 May 1998 13:16:00 -0000	[thread overview]
Message-ID: <199805012016.QAA10541@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980501220036.256A-100000@bartlet.df.lth.se>

   Date: Fri, 1 May 1998 22:02:20 +0200 (MET DST)
   From: Krister Walfridsson <cato@df.lth.se>

   In our exec header, there is a flag that tells if the code in the file
   is position independent. Should I add this to the flags in BFD, or is 
   this attribute obscure enough to keep only as private data in the a.out
   backend?

I think that is meaningful enough that it could be added to the list
of BFD flags.  The main reason it is not there right now is that most
targets which have a notion of position independent support do not
mention it in the program header, so there is no easy way for BFD to
know whether the flag applies.

   Are there any hooks I have missed that can solve my problems? As far I can 
   see, the hooks are present on a too high level, so I end up duplicating 
   nearly the whole aoutx.h. Or should I try to add new hooks?

You should add new hooks.  The hooks which exist right now are there
because they were useful for SunOS, not because they were designed in
any intelligent fashion.  Don't hesitate to add new hook functions
where you need them.

   By the way, are this mailing list the correct place to discuss changes to
   ld, or are there a ld list somewhere?

This is the right mailing list.

Ian

      reply	other threads:[~1998-05-01 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-01 13:02 Krister Walfridsson
1998-05-01 13:16 ` Ian Lance Taylor [this message]

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=199805012016.QAA10541@subrogation.cygnus.com \
    --to=ian@cygnus.com \
    --cc=bfd@cygnus.com \
    --cc=cato@df.lth.se \
    /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).