cc/gcc: do not use the core pass-2 to build the baremetal compiler

In case we build a baremetal compiler, use the standard passes:
- core_cc is used to build the C library;
- as such, it is meant to run on build, not host;
- the final compiler is meant to run on host;

As the current final compiler step can not build a baremetal compiler,
call the core backend from the final step.

NB: Currently, newlib is built during the start_files pass, so we have
to have a core compiler by then... Once we can build the baremetal
compiler from the final cc step, then we can move the newlib build to
the proper step, and then get rid of the core pass-1 static compiler...

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

# Compute MIPS-specific values

CT_DoArchTupleValues() {

    # The architecture part of the tuple, override only for 64-bit

    if [ "${CT_ARCH_64}" = "y" ]; then

        CT_TARGET_ARCH="mips64${target_endian_el}"

    else

        # The architecture part of the tuple:

        CT_TARGET_ARCH="${CT_ARCH}${target_endian_el}"

    fi

    # Override CFLAGS for endianness:

    case "${CT_ARCH_ENDIAN}" in

        big)    CT_ARCH_ENDIAN_CFLAG="-EB";;

        little) CT_ARCH_ENDIAN_CFLAG="-EL";;

    esac

    # Override ABI flags

    CT_ARCH_ABI_CFLAG="-mabi=${CT_ARCH_mips_ABI}"

    CT_ARCH_WITH_ABI="--with-abi=${CT_ARCH_mips_ABI}"

}