From: DJ Delorie <dj@redhat.com>
To: aaron98wiridge9@aaronwl.com
Cc: hanzac@gmail.com, binutils@sources.redhat.com
Subject: Re: Strange flag in WIN32 PECOFF
Date: Tue, 15 Mar 2005 18:30:00 -0000 [thread overview]
Message-ID: <200503151830.j2FIUNV3001110@greed.delorie.com> (raw)
In-Reply-To: <4236B866.2000200@aaronwl.com> (aaron98wiridge9@aaronwl.com)
> I would suspect, without really knowing, that either PECOFF or
> DJGPP's COFF implementation is incorrect with regards to the
> original COFF specification.
Since COFF is otherwise pretty much dead, "correct" is a nebulous
term. DJGPP's COFF matched what all the other binutils coff's were
doing back then (i386-coff was a popular embedded target), but that
doesn't mean it's "correct". PECOFF matches what Microsoft was
producing for Windows, but that doesn't mean it's "correct" either.
The binutils tool "just know" which format they're expecting, so it's
never been a problem before. In general, you can't just link DJGPP
objects and PECOFF objects together. COFF differences aside, the
code's semantics just won't merge well.
prev parent reply other threads:[~2005-03-15 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 23:35 Hanzac Chen
2005-03-15 0:22 ` Aaron W. LaFramboise
2005-03-15 3:20 ` DJ Delorie
2005-03-15 9:51 ` Hanzac Chen
2005-03-15 10:26 ` Aaron W. LaFramboise
2005-03-15 11:05 ` Hanzac Chen
2005-03-15 18:30 ` DJ Delorie [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=200503151830.j2FIUNV3001110@greed.delorie.com \
--to=dj@redhat.com \
--cc=aaron98wiridge9@aaronwl.com \
--cc=binutils@sources.redhat.com \
--cc=hanzac@gmail.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).