search for: r_mips_call16

Hi, There are more than one MIPS relocations which need GOT entry creation. Let's consider two of them R_MIPS_GOT16 and R_MIPS_CALL16 [1]. R_MIPS_GOT16 is applicable to local and external symbols and performs a different calculation in each cases [2]. R_MIPS_CALL16 is applicable to external symbols only and a linker should show an error if it finds R_MIPS_CALL16 with a local target. Now LLD in the `InputSectionBase<ELFT>::r...

...dressAlign: 16 Flags: [SHF_ALLOC] - Name: .rel.text Type: SHT_REL Info: .text AddressAlign: 4 Relocations: - !Relocation Offset: 0x1 SymbolName: glob1 Type: R_MIPS_32 - !Relocation Offset: 0x2 SymbolName: glob2 Type: R_MIPS_CALL16 ]] -- Simon Atanasyan

...t; AddressAlign: 4 > > Relocations: > > - !Relocation > > Offset: 0x1 > > SymbolName: glob1 > > Type: R_MIPS_32 > > - !Relocation > > Offset: 0x2 > > SymbolName: glob2 > > Type: R_MIPS_CALL16 > > ]] > > > > -- > > Simon Atanasyan > > Explicitly modeling relocation sections is correct here. Just one > thing that would need to change. The yaml reader needs to know that > the structure of SHT_REL sections is different, so it would be: > > [[ > S...

Hi, As far as I understand now it is impossible to generate ELF object file with relocation sections using yaml2obj tool. I plan to support ELF relocations in the yaml2obj. Does anybody work on it already or plan to start this task soon? -- Simon Atanasyan