Add the latest gcc-4.3.3 with the forward-ported patchset from gcc-4.3.2.

/trunk/patches/gcc/4.3.3/210-noteGNUstack-00.patch | 47 26 21 0 ++++---
/trunk/patches/gcc/4.3.3/270-missing-execinfo_h.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/260-uclibc-conf-noupstream.patch | 13 9 4 0 +-
/trunk/patches/gcc/4.3.3/220-noteGNUstack-01.patch | 97 51 46 0 +++++++-------
/trunk/patches/gcc/4.3.3/240-pr25343.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/100-alpha-mieee-default.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/230-pr34571.patch | 23 8 15 0 +--
/trunk/patches/gcc/4.3.3/350-sh-without-headers.patch | 17 10 7 0 +-
/trunk/patches/gcc/4.3.3/330-unwind-for-uClibc.patch | 19 12 7 0 ++-
/trunk/patches/gcc/4.3.3/190-libstdc++-pic.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/150-sparc64-bsd.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/290-index_macro.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/140-netbsd-symbolic.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/110-trampolinewarn.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/160-flatten-switch-stmt-00.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/280-c99-complex-ugly-hack.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/300-libmudflap-susv3-legacy.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/170-libiberty-pic.patch | 11 8 3 0 +-
/trunk/patches/gcc/4.3.3/250-sh-pr24836.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/120-java-nomulti.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/320-alpha-signal_h.patch | 14 10 4 0 +-
/trunk/patches/gcc/4.3.3/180-superh-default-multilib.patch | 13 9 4 0 +-
/trunk/patches/gcc/4.3.3/340-make-mno-spe-work-as-expected.patch | 41 23 18 0 +++---
/trunk/patches/gcc/4.3.3/200-pr24170.patch | 23 14 9 0 ++-
/trunk/patches/gcc/4.3.3/310-arm-softfloat.patch | 17 11 6 0 +-
/trunk/patches/gcc/4.3.3/130-cross-compile.patch | 23 14 9 0 ++-
/trunk/config/cc/gcc.in | 7 7 0 0 +
27 files changed, 334 insertions(+), 210 deletions(-)

# Options specific to logging

comment "Logging"

choice

    bool

    prompt "Maximum log level to see:"

    default LOG_INFO if !DEBUG_CT

    default LOG_DEBUG if DEBUG_CT

config LOG_ERROR

    bool

    prompt "ERROR"

    help

      The build will be silent.

      Only if there is an error will you see a message.

config LOG_WARN

    bool

    prompt "WARN"

    help

      The same as above, plus warnings.

config LOG_INFO

    bool

    prompt "INFO"

    help

      The same as above, plus informational messages (main steps).

config LOG_EXTRA

    bool

    prompt "EXTRA"

    help

      The same as above, plus extra messages (sub-steps).

config LOG_DEBUG

    bool

    prompt "DEBUG"

    help

      The same as above, plus lots of crosstool-NG debug information.

config LOG_ALL

    bool

    prompt "ALL"

    help

      The same as above, plus all components build messages (very noisy!).

endchoice

config LOG_LEVEL_MAX

    string

    default "ERROR"   if LOG_ERROR

    default "WARN"    if LOG_WARN

    default "INFO"    if LOG_INFO

    default "EXTRA"   if LOG_EXTRA

    default "DEBUG"   if LOG_DEBUG

    default "ALL"     if LOG_ALL

config LOG_SEE_TOOLS_WARN

    bool

    prompt "Warnings from the tools' builds"

    default n

    depends on ! LOG_ERROR

    help

      Treat warnings from the different tools as crosstool-NG warnings.

      If you say 'y' here, then those warnings will be prefixed with

      '[WARN ]' instead of the default '[ALL  ]'.

      You can safely say 'n' here. Those warnings will anyway be

      recorded in the log file (provided you configured one).

      Tools error will always be logged as crosstool-NG errors.

config LOG_PROGRESS_BAR

    bool

    prompt "Progress bar"

    default y

    depends on ! LOG_ALL

    help

      If you say 'y' here, you'll be able to see the elapsed time.

      As a bonus, you'll also get a rotating bar (/-\|) showing you

      that the build is not stalled (the bar rotates 1/4 every 10 lines

      of components build log).

      Note that the elapsed time can stall for a little while if a

      component has long commands, as the elapsed time is only updated

      each line.

config LOG_TO_FILE

    bool

    prompt "Log to a file"

    default y

    help

      Save *full* logs to a file. Even log levels you didn't specify above

      will be available in this file. The log file will be named build.log

      and stored in the toolchain prefix dir (set above).

      Definitely, say Y.

config LOG_FILE_COMPRESS

    bool

    prompt "Compress the log file"

    default y

    depends on LOG_TO_FILE

    help

      Compress the log file once the toolchain is successfully built.