From: Hanzac Chen <hanzac@gmail.com>
To: binutils@sources.redhat.com
Cc: aaron98wiridge9@aaronwl.com
Subject: Re: Strange flag in WIN32 PECOFF
Date: Tue, 15 Mar 2005 11:05:00 -0000 [thread overview]
Message-ID: <4236C13B.1010508@gmail.com> (raw)
In-Reply-To: <4236B866.2000200@aaronwl.com>
Hi, Aaron
Aaron W. LaFramboise wrote:
> ...
> I would suspect, without really knowing, that either PECOFF or DJGPP's
> COFF implementation is incorrect with regards to the original COFF
> specification. This is probably the root of the problem. However, I
> don't think it is possible to fix this.
> ...
Is it because that the PECOFF format should follow the Microsoft's
specification? If that, I don't think it will do good. Moreover, barely
the compatibility in the formats is not enough, MSVC produces objects
that have too much *features* especially the C++ ones. IMHO, only the
PE *executale* file strictly following the specification is enough.
and the objects could be compatible with the DJGPP's.
only suggestion,
Hanzac
next prev parent reply other threads:[~2005-03-15 11:05 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 [this message]
2005-03-15 18:30 ` DJ Delorie
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=4236C13B.1010508@gmail.com \
--to=hanzac@gmail.com \
--cc=aaron98wiridge9@aaronwl.com \
--cc=binutils@sources.redhat.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).