[Bug ld/4643] linker scripts do not accept symbols in MEMORY section

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=4643

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by Alan Modra <address@hidden>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cc9ad334a71b0c032f711e86885fb73821f3be16

commit cc9ad334a71b0c032f711e86885fb73821f3be16
Author: Senthil Kumar Selvaraj <address@hidden>
Date:   Wed Jan 28 15:01:50 2015 +1030

    Allow symbols in MEMORY region specification

    This patch fixes PR 4643 by allowing symbols in the LENGTH and ORIGIN
    fields of MEMORY regions.  Previously, only constants and constant
    expressions are allowed.

    For the AVR target, this helps define memory constraints more
    accurately (per device), without having to create a ton of device
    specific linker scripts.

    ld/
        PR 4643
        * ldexp.c (fold_name): Fold LENGTH only after
        lang_first_phase_enum.
        * ldgram.y (memory_spec): Don't evaluate ORIGIN and LENGTH
        rightaway.
        * ldlang.h (struct memory_region_struct): Add origin_exp and
        length_exp fields.
        * ldlang.c (lang_do_memory_regions): New.
        (lang_memory_region_lookup): Initialize origin_exp and
        length_exp fields.
        (lang_process): Call lang_do_memory_regions.
    ld/testsuite/
        * ld-scripts/memory.t: Define new symbol tred.
        * ld-scripts/memory_sym.t: New.
        * ld-scripts/script.exp: Perform MEMORY with symbols test, and
        conditionally check values of linker symbols.

-- 
You are receiving this mail because:
You are on the CC list for the bug.