TODO
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jul 17 22:43:07 2011 +0200 (2011-07-17)
changeset 2893 a8a65758664f
parent 1731 648fcf1f4568
child 3306 80e46e644bc0
permissions -rw-r--r--
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>
     1 This is a somewhat ordered TODO list:
     2 
     3 Recurring tasks:
     4 
     5 - update versions for every tools...
     6 
     7 - update and/or upgrade all samples
     8 
     9 
    10 Non-recurring tasks:
    11 
    12 - update newlib (for enhanced bare metal)
    13   - confirm existing implementation on targets other than AVR32
    14   - try to make it generic, will help for uClibc++
    15 
    16 - multilib
    17 
    18 - Cygwin target (needs newlib)
    19   - so we can build toolchains that generate code for Windows/Cygwin
    20 
    21 - Cygwin host
    22   - so we can build toolchains that run natively under Windows/Cygwin
    23 
    24 - mingw32 target
    25   - so we can build toolchains that generate code for Windows/Win32
    26 
    27 - mingw32 host
    28   - so we can build toolchains that run natively under Windows/Win32
    29     (without requiring Cygwin)
    30 
    31 - uClibc++
    32   - see newlib, above
    33 
    34 - uClinux
    35   - check whether we can use newlib under uClinux (?)