search for: 0000074c

...f -r z29.gas.o Relocation section '.rel.text' at offset 0x4584 contains 705 entries: Offset Info Type Sym.Value Sym. Name ... 00000748 00000409 R_MIPS_GOT16 00000000 .bss // %got(scope_top) 00000750 00000406 R_MIPS_LO16 00000000 .bss // %lo(scope_top) 0000074c 00000409 R_MIPS_GOT16 00000000 .bss // %got(body_ok) 00000754 00000406 R_MIPS_LO16 00000000 .bss // %lo(body_ok) The attached patch makes the following changes to make direct object emitter write out relocations in the correct order: 1. Add a target hook MCELFObjectTargetWriter:...

...n section '.rel.text' at offset 0x4584 contains 705 entries: >  Offset     Info    Type            Sym.Value  Sym. Name > ... > 00000748  00000409 R_MIPS_GOT16      00000000   .bss // %got(scope_top) > 00000750  00000406 R_MIPS_LO16       00000000   .bss   // %lo(scope_top) > 0000074c  00000409 R_MIPS_GOT16      00000000   .bss // %got(body_ok) > 00000754  00000406 R_MIPS_LO16       00000000   .bss // %lo(body_ok) > > > The attached patch makes the following changes to make direct object > emitter write out relocations in the correct order: > > 1. Add a targ...

...text' at offset 0x4584 contains 705 entries: >> Offset Info Type Sym.Value Sym. Name >> ... >> 00000748 00000409 R_MIPS_GOT16 00000000 .bss // %got(scope_top) >> 00000750 00000406 R_MIPS_LO16 00000000 .bss // %lo(scope_top) >> 0000074c 00000409 R_MIPS_GOT16 00000000 .bss // %got(body_ok) >> 00000754 00000406 R_MIPS_LO16 00000000 .bss // %lo(body_ok) >> >> >> The attached patch makes the following changes to make direct object >> emitter write out relocations in the correct order: &...

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

...0x4584 contains 705 entries: >>>  Offset     Info    Type            Sym.Value  Sym. Name >>> ... >>> 00000748  00000409 R_MIPS_GOT16      00000000   .bss // %got(scope_top) >>> 00000750  00000406 R_MIPS_LO16       00000000   .bss   // %lo(scope_top) >>> 0000074c  00000409 R_MIPS_GOT16      00000000   .bss // %got(body_ok) >>> 00000754  00000406 R_MIPS_LO16       00000000   .bss // %lo(body_ok) >>> >>> >>> The attached patch makes the following changes to make direct object >>> emitter write out relocations in th...

...entries: >>>> Offset Info Type Sym.Value Sym. Name >>>> ... >>>> 00000748 00000409 R_MIPS_GOT16 00000000 .bss // %got(scope_top) >>>> 00000750 00000406 R_MIPS_LO16 00000000 .bss // %lo(scope_top) >>>> 0000074c 00000409 R_MIPS_GOT16 00000000 .bss // %got(body_ok) >>>> 00000754 00000406 R_MIPS_LO16 00000000 .bss // %lo(body_ok) >>>> >>>> >>>> The attached patch makes the following changes to make direct object >>>> emitter write...

...1) ret=5f401018 08067ca0:Ret kernel32.TlsGetValue() retval=40378dbc ret=5f401018 08067ca0:Call kernel32.TlsGetValue(00000001) ret=5f401018 08067ca0:Ret kernel32.TlsGetValue() retval=40378dbc ret=5f401018 08067ca0:Call user32.GetParent(00001840) ret=5f401281 08067ca0:Ret user32.GetParent() retval=0000074c ret=5f401281 08067ca0:Call user32.GetScrollPos(00001914,00000000) ret=5f4034ca 08067ca0:Ret user32.GetScrollPos() retval=00000000 ret=5f4034ca 08067ca0:Call user32.GetWindowLongA(00001914,fffffff0) ret=5f402173 08067ca0:Ret user32.GetWindowLongA() retval=50200000 ret=5f402173 08067ca0:Call user32...