From: DJ Delorie <dj@delorie.com>
To: ian@zembu.com
Cc: snowball3@bigfoot.com, binutils@sourceware.cygnus.com
Subject: Re: .gnu.linkonce COFF support
Date: Wed, 14 Jul 1999 04:32:00 -0000 [thread overview]
Message-ID: <199907141132.HAA22001@indy.delorie.com> (raw)
In-Reply-To: <19990714021852.9180.qmail@daffy.airs.com>
> 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.
There are two ways of implementing long section names in COFF: the gnu
way, and the PE way. We got that wrong too. The GNU way is to store
the name in the string table. The PE way is to use multiple auxents.
As far as *using* long section names for various features, that's OK
with me, except for the COMDAT thing.
Not, of course, that I care about what MS's format says, since djgpp
is independent of PE, but I'd hate to see us do the work twice if we
can do it once for both platforms.
next prev parent reply other threads:[~1999-07-14 4:32 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
1999-07-14 4:32 ` DJ Delorie [this message]
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=199907141132.HAA22001@indy.delorie.com \
--to=dj@delorie.com \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.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).