public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: dj@delorie.com
Cc: snowball3@bigfoot.com, binutils@sourceware.cygnus.com
Subject: Re: .gnu.linkonce COFF support
Date: Tue, 13 Jul 1999 19:20:00 -0000	[thread overview]
Message-ID: <19990714021852.9180.qmail@daffy.airs.com> (raw)
In-Reply-To: <199907140145.VAA06257@indy.delorie.com>

   Date: Tue, 13 Jul 1999 21:45:49 -0400 (EDT)
   From: DJ Delorie <dj@delorie.com>

   > Some questions about possibilities for DJGPP COFF. Would enabling 
   > .gnu.linkonce.* for DJGPP COFF improve template support much over 
   > what weak symbols do already? This would require enabling the long 
   > section name feature (> 8 characters) , but it can be turned on by one 
   > line.

   The "long section name feature" is a remnant from PE's specs, and
   binutils doesn't implement it properly.  The right way is to use a
   specially designated symbol (usually the function name's symbol) as
   the unique id, not the section name.  I would discourage adding broken
   support to DJGPP when it needs to be fixed for PE anyway.  If you want
   to go this route, figure out how to do it the right way (the MS PE
   way) so that we won't have to jump through hoops later when the PE
   support is fixed.

I'm not sure this is quite right.

The COMDAT section support in the binutils is wrong, and it does work
the way you say.

The long section name support is different and unrelated.  As far as I
know, the binutils support long section names as they are used and
generated by the Microsoft tools.

I took Mark's question to be literally about .gnu.linkonce.*, as in
the GNU extension to ELF, which was perhaps an error.  It's true that
I wouldn't recommend using PE style COMDAT sections right now, since
that work will change.

Ian

  reply	other threads:[~1999-07-13 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-13 14:42 Mark E.
1999-07-13 14:55 ` Ian Lance Taylor
1999-07-13 18:45 ` DJ Delorie
1999-07-13 19:20   ` Ian Lance Taylor [this message]
1999-07-14  4:32     ` DJ Delorie
1999-07-14 17:02       ` Ian Lance Taylor
1999-07-14 17:04         ` Mark E.
1999-07-13 21:22   ` Mark E.

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=19990714021852.9180.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=dj@delorie.com \
    --cc=snowball3@bigfoot.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).