mips r6 relocations

[composerguy]

I work at Imagination/Mips.

I've been tasked to add the r6 relocations for mips32 and mips64.

One thing I need to do is to check that the user is not mixing .o files for non r6 and for r6.

There is information in the .o file header that determines this.

Any thoughts of the based way to check for this consistency?

I have several ideas of where this can go but those from the core developers are likely

to know best where it goes.

Tia.

Reed 

[reed kotler]

There does not seem to be any checking for any of the mclinker targets to make sure the the .o files are consistent with the target triple.

There is also no way to do consistency checking or to look at the e_flags from the ELF_hdr section

--
You received this message because you are subscribed to the Google Groups "MCLinker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mclinker+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Pete Chou]

Hi Reed,

If linking against object files that are different with the target triple, a warning of incompatible format would be issued and those object files would not be included in the linking.

Please check ELFObjectReader::isMyFormat() in lib/LD/ELFObjectReader.cpp. In this function, some elf attributes such as type, endian, machine are checked. You may add checking for flags here.

Thanks,

Pete

[reed kotler]

I did not hear back so I had started to make the change by a virtual MergeFlags method to GNULDBackend and then overriding this method in MipsGNULDBackend.

The isMyFormat seems to have a different purpose; i.e. checking that the object type is recognized.