This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [arm] Implement soft-float abi



On Tue, 24 Aug 2004, Richard Earnshaw wrote:


The thread starts here:

http://sources.redhat.com/ml/binutils/2004-08/msg00029.html

I don't mind if the compatibility information is in the ELF header, or in a dedicated section. Also if it's described by strings or by binary bit-maps is just a technical issue.


What I think is useful to have is the ability that the linker(s) will refuse to combine objects which have incompatible features, while also having the option "--no-warn-mismatch" for people who know what they're doing.

I could suggest some small addition: after GCC passes ".feature xxx" lines to GAS and they find their way in the ELF file, LD should use a script file (parsed runtime on each invocation) which describes how the different features relate to each other. Standard script will include normal features like architecture, thumb interworking, ABI, FP instructions, etc, *but* the users should be able to include their own relations. For example, I will be very happy if I can mark the objects with the type of MaverickCrunch workarounds they're for and don't mix between different types. Hopefully other people may have their personal needs, too.

Option "--no-warn-mismatch" will ignore this script, or at least just print warnings without them being fatal.

How does this sound to you?

-- Vladimir


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