[coreboot-gerrit] Patch merged into coreboot/master: 99ac98f Introduce stage-specific architecture for coreboot

the following patch was just integrated into master:
commit 99ac98f7e1fa30d3fb33cc5486e6af46b4bef56e
Author: Furquan Shaikh 
Date:   Wed Apr 23 10:18:48 2014 -0700

Introduce stage-specific architecture for coreboot

Make all three coreboot stages (bootblock, romstage and ramstage) aware of the
    architecture specific to that stage i.e. we will have CONFIG_ARCH variables for
    each of the three stages. This allows us to have an SOC with any combination of
    architectures and thus every stage can be made to run on a completely different
    architecture independent of others. Thus, bootblock can have an x86 arch whereas
    romstage and ramstage can have arm32 and arm64 arch respectively. These stage
    specific CONFIG_ARCH_ variables enable us to select the proper set of toolchain
    and compiler flags for every stage.

These options can be considered as either arch or modes eg: x86 running in
    different modes or ARM having different arch types (v4, v7, v8). We have got rid
    of the original CONFIG_ARCH option completely as every stage can have any
    architecture of its own. Thus, almost all the components of coreboot are
    identified as being part of one of the three stages (bootblock, romstage or
    ramstage). The components which cannot be classified as such e.g. smm, rmodules
    can have their own compiler toolset which is for now set to *_i386. Hence, all
    special classes are treated in a similar way and the compiler toolset is defined
    using create_class_compiler defined in Makefile.

In order to meet these requirements, changes have been made to CC, LD, OBJCOPY
    and family to add CC_bootblock, CC_romstage, CC_ramstage and similarly others.
    Additionally, CC_x86_32 and CC_armv7 handle all the special classes. All the
    toolsets are defined using create_class_compiler.

Few additional macros have been introduced to identify the class to be used at
    various points, e.g.: CC_$(class) derives the $(class) part from the name of
    the stage being compiled.

We have also got rid of COREBOOT_COMPILER, COREBOOT_ASSEMBLER and COREBOOT_LINKER
    as they do not make any sense for coreboot as a whole. All these attributes are
    associated with each of the stages.

Change-Id: I923f3d4fb097d21071030b104c372cc138c68c7b
    Signed-off-by: Furquan Shaikh 
    Reviewed-on: http://review.coreboot.org/5577
    Tested-by: build bot (Jenkins)
    Reviewed-by: Aaron Durbin

See http://review.coreboot.org/5577 for details.

-gerrit