cc/gcc: add the backend/frontend infra for final gcc

Currently, we issue the bare-metal compiler from the pass_1 & pass_2
core compilers, because the final gcc breaks while doing so.

This implies we have to build some libces during the start_files step,
instead of the standard libc step. This is the case for newlib.

By adding a backend/frontend infra to the final gcc, we can abstract
what backend to call: the standard backend for non-bare-metal gcc,
and the core backend for bare-metal.

This patch is just an no-op, it just adds the final backend and
frontend without changing the way bare-metal is built, to come in a
subsequent patch.

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

 diff -durN glibc-2.7.orig/Makerules glibc-2.7/Makerules

 --- glibc-2.7.orig/Makerules	2007-08-26 04:18:03.000000000 +0200

 +++ glibc-2.7/Makerules	2008-07-28 15:17:27.000000000 +0200

 @@ -1203,6 +1203,9 @@

  # The include magic above causes those files to use this variable for flags.

  CPPFLAGS-nonlib = -DNOT_IN_libc=1

 +ifneq ($(OBJDUMP_FOR_HOST),)

 +OBJDUMP = $(OBJDUMP_FOR_HOST)

 +endif

  ifeq ($(versioning),yes)

  # Generate normalized lists of symbols, versions, and data sizes.