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: XCOFF 64 function address wrong?


> The target would appear to be the problem.  If the target was:
> 
>    --target=powerpc64-ibm-aix5.2.0.0
> 
> then I think that it should work.
> 

Tried that -- and still the ifdef in coffgen.c is still not happening.
Even tried to do --host the same too..

> [See bfd/config.bfd for where this target is matched.  Look for the 
> targ_defvec and then compare that the list of vectors in 
> bfd/configure.in.  You want one that triggers the inclusion of 
> coff64-rs6000].

But how could coff64-rs6000.c file #defining a value influence coffgen.c
(unless there's some autogeneration going on here)?  Shouldn't this be
in a .h file?  Is there a better test for XCOFF64/32 status than a
compile time ifdef - surely we'd want mixed capability?  


Ta,
David
-- 
David Lecomber <david@allinea.com>


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