search for: z29

...ppear consecutively in the relocation table. As a result, relocations can appear in a different order than the instructions that they're for. For example, in this code, the post-RA scheduler inserts an instruction with relocation %got(body_ok) between %got(scope_top) and %lo(scope_top). $ cat z29.s lw $3, %got(scope_top)($gp) lw $2, %got(body_ok)($gp) lw $3, %lo(scope_top)($3) addiu $2, $2, %lo(body_ok) This is the assembled program generated by gas: $ mips-linux-gnu-objdump -dr z29.gas.o 748: 8f830000 lw v1,0(gp) 748: R_MIPS_GOT1...

...> table. As a result, relocations can appear in a different order than > the instructions that they're for. > > For example, in this code, the post-RA scheduler inserts an > instruction with relocation %got(body_ok) between %got(scope_top) and > %lo(scope_top). > > $ cat z29.s >  lw  $3, %got(scope_top)($gp) >  lw  $2, %got(body_ok)($gp) >  lw  $3, %lo(scope_top)($3) >  addiu $2, $2, %lo(body_ok) > > This is the assembled program generated by gas: > $  mips-linux-gnu-objdump -dr z29.gas.o > >     748:       8f830000        lw      v1,0(gp) &g...

...ations can appear in a different order than >> the instructions that they're for. >> >> For example, in this code, the post-RA scheduler inserts an >> instruction with relocation %got(body_ok) between %got(scope_top) and >> %lo(scope_top). >> >> $ cat z29.s >> lw $3, %got(scope_top)($gp) >> lw $2, %got(body_ok)($gp) >> lw $3, %lo(scope_top)($3) >> addiu $2, $2, %lo(body_ok) >> >> This is the assembled program generated by gas: >> $ mips-linux-gnu-objdump -dr z29.gas.o >> >> 748:...

Hi Akira, If I follow correctly, the relocation entries can thus be in a different order than the instructions that they're for? That seems a bit odd, but I suppose there's nothing inherently wrong with that. It's just not something, AFAIK, that llvm has had to deal with before. This should definitely be a target-specific thing, not a general ELFObjectWriter thing, as other targets

What would be the best way to sort relocation entries before they are written out in ELFObjectWriter::WriteRelocationsFragment? According to the Mips ABI documents I have, there are certain restrictions on the order relocations appear in the table (e.g. R_MIPS_HI16 and R_MIPS_GOT16 must be followed immediately by a R_MIPS_LO16). When I enable post RA scheduling, some of the restrictions are

...ferent order than >>> the instructions that they're for. >>> >>> For example, in this code, the post-RA scheduler inserts an >>> instruction with relocation %got(body_ok) between %got(scope_top) and >>> %lo(scope_top). >>> >>> $ cat z29.s >>>  lw  $3, %got(scope_top)($gp) >>>  lw  $2, %got(body_ok)($gp) >>>  lw  $3, %lo(scope_top)($3) >>>  addiu $2, $2, %lo(body_ok) >>> >>> This is the assembled program generated by gas: >>> $  mips-linux-gnu-objdump -dr z29.gas.o >...

...> the instructions that they're for. >>>> >>>> For example, in this code, the post-RA scheduler inserts an >>>> instruction with relocation %got(body_ok) between %got(scope_top) and >>>> %lo(scope_top). >>>> >>>> $ cat z29.s >>>> lw $3, %got(scope_top)($gp) >>>> lw $2, %got(body_ok)($gp) >>>> lw $3, %lo(scope_top)($3) >>>> addiu $2, $2, %lo(body_ok) >>>> >>>> This is the assembled program generated by gas: >>>> $ mips-linux-g...

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

...0 0.04 443077 z22.ll 12 1244660 0 0.09 1244626 0 0.10 1244626 z23.ll 3 656308 0 0.06 656274 0 0.05 656274 z24.ll 0 34384 0 0.01 34350 0 0.01 34350 z25.ll 0 451 0 0.01 417 0 0.01 417 z26.ll 3 51862 0 0.01 51828 0 0.01 51828 z27.ll 0 451 0 0.01 417 0 0.01 417 z28.ll 7 31253 0 0.01 31219 0 0.01 31219 z29.ll 22 359555 0 0.04 359521 0 0.03 359521 z30.ll 7 47515 0 0.01 47481 0 0.01 47481 z31.ll 2 20707 0 0.01 20673 0 0.01 20673 z32.ll 1 53550 0 0.01 53516 0 0.01 53516 z33.ll 13 328775 0 0.03 328741 0 0.04 328741 z34.ll 1 20742 0 0.01 20708 0 0.01 20708 z35.ll 3 410621 0 0.03 410587 0 0.04 410587 z36.l...