This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Strange flag in WIN32 PECOFF


Hanzac Chen wrote:

> So it's the PE work's problem. :-)
> But anyway I think since the two COFF outputs are supported by the
> binutils, they at least should be compatible when they are not the
> final executables so that they can be linked by the both binutils'
> targets. It will be great. and it will be easier for those who are
> drilling in the OS level and linker level. :-)

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.

One would assume, though, there would be some way to distinguish PECOFF
objects from other sorts of objects.  I can't think of any particular
method offhand, though.  You might try assembling an object with
binutils assemblers for both targets, and seeing if objdump reports any
interesting differences.


Aaron W. LaFramboise


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]