public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: snowball3@usa.net
Cc: gas2@cygnus.com
Subject: Re: COFF weak symbols
Date: Sat, 03 Oct 1998 09:03:00 -0000	[thread overview]
Message-ID: <199810031603.MAA17471@subrogation.cygnus.com> (raw)
In-Reply-To: <199810031525.PAA100700@out4.ibm.net>

   From: "Mark E." <snowball3@usa.net>
   Date: Sat, 3 Oct 1998 11:25:18 +0000

   I'm interested have added or in adding an extension to COFF (or at 
   least DJGPP's COFF) to have weak symbols. I've already added 
   the .weak directive to the Oct 1st snapshot, but I wanted to check 
   and see how you wanted me proceed (or even if I should 
   proceed). I'm not an object file expert, but I know just enough to 
   know I want weak symbols. The linker already seems to support 
   weak symbols, it would just be a matter of deciding where in the 
   symbol record to store the weak symbol bit (though I have an idea).

   I tried e-mailing Ian but he seems to be on vacation.

You only sent me the mail Thursday evening.  I can certainly
sympathize with how it feels when you don't get an immediate reply to
your mail--I've been there myself--but the reality is that dealing
with binutils issues from the net is an unpaid activity for me, so
there is no guaranteed response time.  As I expect you've already
seen, I replied to your message earlier this morning.

Of course, unless you need my personal input, which for an issue like
this you don't, it's probably better to send such a message to the
mailing list in the first.

The main issue with any extension like this is how to store the
information in the object file.  Once that has been determined, you
need to enhance BFD to transfer the information between the generic
internal format and the object file external format.

For COFF, I would recommend defining a new storage class C_WEAK as a
parallel to C_EXT and C_STAT.  It should be moderately straightforward
to add BFD, assembler, and linker support for this.

Ian

  reply	other threads:[~1998-10-03  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-03  8:25 Mark E.
1998-10-03  9:03 ` Ian Lance Taylor [this message]
1998-10-03 10:35   ` Mark E.
1998-10-03 20:47 ` Robert Lipe

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=199810031603.MAA17471@subrogation.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=snowball3@usa.net \
    /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).