[lkml]   [2009]   [Dec]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH] Valid relocation symbol for FLAT format on ARM, v2
    See attachment.


    Apparently newer GCC would generate ANCHOR symbols beyond the end of
    data/bss segment on ARM CPUs. As a result, the exiting validity checking
    for relocation symbols in FLAT format will fail.

    Signed-off-by: Jun Sun <>

    diff -Nru linux- linux-
    --- linux- 2009-12-18 14:27:07.000000000 -0800
    +++ linux- 2009-12-31 17:08:28.000000000 -0800
    @@ -7,7 +7,12 @@

    #define flat_argvp_envp_on_stack() 1
    #define flat_old_ram_flag(flags) (flags)
    -#define flat_reloc_valid(reloc, size) ((reloc) <= (size))
    +#define flat_reloc_valid(reloc, size) ((reloc) <= (size) + 0x1000)
    +/* [jsun] new gcc 4.x generates ANCHOR symbols in order to reduce the size
    + * of GOT table for PIC code. It is possible the ANCHOR is placed beyond
    + * the end of data/bss segment up to 4K bytes(12 bits), because ARM allows
    + * negative 12-bit offset. Thus we allow 0x1000 extra in reloc address range.
    + */
    #define flat_get_addr_from_rp(rp, relval, flags, persistent) get_unaligned(rp)
    #define flat_put_addr_at_rp(rp, val, relval) put_unaligned(val,rp)
    #define flat_get_relocate_addr(rel) (rel)
     \ /
      Last update: 2010-01-01 02:29    [W:0.019 / U:0.664 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site