Bring in a trimmed down gcc-3.4-20040618.
authorMatthew Dillon <dillon@dragonflybsd.org>
Sun, 20 Jun 2004 02:14:58 +0000 (02:14 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Sun, 20 Jun 2004 02:14:58 +0000 (02:14 +0000)
Submitted-by: Joerg Sonnenberger <joerg@crater.dragonflybsd.org>
1044 files changed:
contrib/gcc-3.4/BUGS [new file with mode: 0644]
contrib/gcc-3.4/COPYING [new file with mode: 0644]
contrib/gcc-3.4/COPYING.LIB [new file with mode: 0644]
contrib/gcc-3.4/FAQ [new file with mode: 0644]
contrib/gcc-3.4/LAST_UPDATED [new file with mode: 0644]
contrib/gcc-3.4/MAINTAINERS [new file with mode: 0644]
contrib/gcc-3.4/README [new file with mode: 0644]
contrib/gcc-3.4/README.DELETED [new file with mode: 0644]
contrib/gcc-3.4/README.DRAGONFLY [new file with mode: 0644]
contrib/gcc-3.4/README.SCO [new file with mode: 0644]
contrib/gcc-3.4/gcc/COPYING [new file with mode: 0644]
contrib/gcc-3.4/gcc/COPYING.LIB [new file with mode: 0644]
contrib/gcc-3.4/gcc/SERVICE [new file with mode: 0644]
contrib/gcc-3.4/gcc/alias.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/alloc-pool.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/alloc-pool.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/attribs.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/basic-block.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/bb-reorder.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/bitmap.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/bitmap.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/bt-load.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/builtin-attrs.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/builtin-types.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/builtins.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/builtins.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-aux-info.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-common.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-common.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-common.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-config-lang.in [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-convert.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-cppbuiltin.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-decl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-dump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-errors.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-format.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-incpath.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-incpath.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-lang.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-lex.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-objc-common.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-opts.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-parse.in [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-pch.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-ppoutput.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-pragma.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-pragma.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-pretty-print.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-pretty-print.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-semantics.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-tree.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/c-typeck.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/c.opt [new file with mode: 0644]
contrib/gcc-3.4/gcc/caller-save.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/calls.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfg.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfganal.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgbuild.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgcleanup.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfghooks.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfghooks.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfglayout.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfglayout.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgloop.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgloop.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgloopanal.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgloopmanip.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cfgrtl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cgraph.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cgraph.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cgraphunit.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/collect2.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/collect2.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/combine.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/common.opt [new file with mode: 0644]
contrib/gcc-3.4/gcc/conditions.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/README [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/dbxelf.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/elfos.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/athlon.md [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/att.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/biarch64.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/bsd.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/emmintrin.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/gas.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/i386-modes.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/i386-protos.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/i386.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/i386.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/i386.md [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/i386elf.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/k6.md [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/mmintrin.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/pentium.md [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/pmmintrin.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/ppro.md [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/unix.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/x86-64.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/config/i386/xmmintrin.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/conflict.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/convert.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/convert.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/coretypes.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/coverage.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/coverage.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/call.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cfns.gperf [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cfns.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/class.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cp-lang.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cp-tree.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cp-tree.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cvt.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cxx-pretty-print.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/cxx-pretty-print.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/decl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/decl.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/decl2.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/dump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/error.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/except.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/expr.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/friend.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/g++spec.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/init.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/lang-specs.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/lex.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/lex.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/mangle.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/method.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/name-lookup.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/name-lookup.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/operators.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/optimize.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/parser.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/pt.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/ptree.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/repo.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/rtti.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/search.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/semantics.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/tree.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/typeck.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cp/typeck2.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppcharset.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppdefault.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppdefault.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpperror.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppexp.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppfiles.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpphash.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpphash.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppinit.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpplex.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpplib.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpplib.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppmacro.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpppch.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppspec.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cpptrad.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppucnid.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppucnid.pl [new file with mode: 0644]
contrib/gcc-3.4/gcc/cppucnid.tab [new file with mode: 0644]
contrib/gcc-3.4/gcc/crtstuff.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cse.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cselib.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/cselib.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/cstamp-h.in [new file with mode: 0644]
contrib/gcc-3.4/gcc/dbxout.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/dbxout.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/debug.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/debug.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/defaults.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/df.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/df.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/diagnostic.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/diagnostic.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/diagnostic.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/bugreport.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/c-tree.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/collect2.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/compat.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/configfiles.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/configterms.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/contrib.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/contribute.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/cpp.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/cppenv.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/cppinternals.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/cppopts.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/extend.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/fragments.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/frontends.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/gcc.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/gccint.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/gcov.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/gnu.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/gty.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/headerdirs.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/hostconfig.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/include/fdl.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/include/funding.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/include/gcc-common.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/include/gpl.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/include/texinfo.tex [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/install-old.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/install.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/install.texi2html [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/interface.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/invoke.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/languages.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/libgcc.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/makefile.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/md.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/objc.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/passes.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/portability.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/rtl.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/service.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/sourcebuild.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/standards.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/tm.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/doc/trouble.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/dojump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/doloop.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/dominance.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/dummy-conditions.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/dwarf.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/dwarf2.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/dwarf2asm.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/dwarf2asm.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/dwarf2out.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/dwarf2out.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/emit-rtl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/errors.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/errors.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/et-forest.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/et-forest.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/except.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/except.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/explow.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/expmed.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/expr.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/expr.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/ansify.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bad.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bad.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bad.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bit.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bit.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bld-op.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bld.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bld.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bugs.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/bugs0.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/com-rt.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/com.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/com.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/data.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/data.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/equiv.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/equiv.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/expr.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/expr.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/ffe.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/fini.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/g77.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/g77spec.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/global.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/global.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/implic.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/implic.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/info-b.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/info-k.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/info-w.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/info.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/info.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/intdoc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/intdoc.in [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/intdoc.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/intrin.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/intrin.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/intrin.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/invoke.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/lab.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/lab.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/lang-specs.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/lang.opt [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/lex.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/lex.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/malloc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/malloc.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/name.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/name.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/news.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/news0.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/parse.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/proj.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/root.texi [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/src.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/src.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/st.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/st.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/sta.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/sta.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stb.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stb.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stc.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/std.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/std.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/ste.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/ste.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/storag.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/storag.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stp.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stp.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-1t.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-2t.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-fo.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-io.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-nq.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-op.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str-ot.fin [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/str.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/sts.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/sts.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stt.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stt.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stu.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stu.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stv.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stv.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stw.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/stw.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/symbol.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/symbol.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/symbol.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/target.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/target.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/top.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/top.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/type.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/type.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/where.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/f/where.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/final.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/fix-header.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/flags.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/flow.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/fold-const.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/fp-test.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/function.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/function.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gbl-ctors.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcc.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gccspec.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcov-dump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcov-io.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcov-io.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcov-iov.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcov.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gcse.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gdbinit.in [new file with mode: 0644]
contrib/gcc-3.4/gcc/gen-protos.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genattr.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genattrtab.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genattrtab.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/genautomata.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gencheck.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gencodes.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genconditions.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genconfig.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genconstants.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genemit.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genextract.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genflags.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gengenrtl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gengtype-lex.l [new file with mode: 0644]
contrib/gcc-3.4/gcc/gengtype-yacc.y [new file with mode: 0644]
contrib/gcc-3.4/gcc/gengtype.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gengtype.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/genmodes.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genmultilib [new file with mode: 0644]
contrib/gcc-3.4/gcc/genopinit.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genoutput.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genpeep.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genpreds.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/genrecog.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gensupport.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gensupport.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/ggc-common.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ggc-none.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ggc-page.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ggc-simple.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ggc-zone.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ggc.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/glimits.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/global.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gmon.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/graph.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/graph.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gstab.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gsyms.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gsyslimits.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-aix.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-dce.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-gnat.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-gnat.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-posix.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-posix.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-rtems.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-single.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-solaris.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-vxworks.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr-win32.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/gthr.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/haifa-sched.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/hard-reg-set.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/hashtable.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/hashtable.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/hooks.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/hooks.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/host-default.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/hosthooks-def.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/hosthooks.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/hwint.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/ifcvt.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/input.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/insn-addr.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/integrate.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/integrate.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/intl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/intl.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/jump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/langhooks-def.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/langhooks.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/langhooks.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/lcm.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/libfuncs.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/libgcc2.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/libgcc2.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/libgcov.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/limitx.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/limity.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/line-map.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/line-map.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/lists.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/local-alloc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/longlong.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/loop-init.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/loop-unroll.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/loop-unswitch.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/loop.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/loop.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/machmode.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/machmode.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/main.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/mips-tdump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/mips-tfile.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/mkdeps.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/mkdeps.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/mode-classes.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/objc/README [new file with mode: 0644]
contrib/gcc-3.4/gcc/objc/lang-specs.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/objc/objc-act.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/objc/objc-act.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/objc/objc-lang.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/objc/objc-tree.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/optabs.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/optabs.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/opts.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/opts.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/opts.sh [new file with mode: 0644]
contrib/gcc-3.4/gcc/output.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/params.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/params.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/params.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/postreload.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/predict.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/predict.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/predict.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/prefix.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/prefix.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/pretty-print.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/pretty-print.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/print-rtl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/print-tree.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/profile.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/protoize.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ra-build.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ra-colorize.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ra-debug.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ra-rewrite.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ra.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/ra.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/read-rtl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/real.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/real.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/recog.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/recog.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/reg-stack.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/regclass.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/regmove.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/regrename.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/regs.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/reload.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/reload.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/reload1.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/reorg.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/resource.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/resource.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/rtl-error.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/rtl.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/rtl.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/rtl.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/rtlanal.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sbitmap.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sbitmap.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/scan-decls.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/scan.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/scan.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/sched-deps.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sched-ebb.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sched-int.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/sched-rgn.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sched-vis.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sdbout.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sdbout.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/sibcall.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/simplify-rtx.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sreal.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sreal.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/stab.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/stack.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/stmt.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/stor-layout.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/stringpool.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/stub-objc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/sys-protos.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/sys-types.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/system.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/target-def.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/target.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/targhooks.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/targhooks.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/timevar.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/timevar.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/timevar.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/tlink.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/toplev.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/toplev.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/tracer.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree-dump.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree-dump.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree-inline.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree-inline.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree-optimize.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree.def [new file with mode: 0644]
contrib/gcc-3.4/gcc/tree.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/tsystem.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/typeclass.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/unroll.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-c.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-dw2-fde-darwin.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-dw2-fde-glibc.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-dw2-fde.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-dw2-fde.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-dw2.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-pe.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind-sjlj.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/unwind.inc [new file with mode: 0644]
contrib/gcc-3.4/gcc/value-prof.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/value-prof.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/varasm.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/varray.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/varray.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/version.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/version.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/vmsdbg.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/vmsdbgout.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/web.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/xcoff.h [new file with mode: 0644]
contrib/gcc-3.4/gcc/xcoffout.c [new file with mode: 0644]
contrib/gcc-3.4/gcc/xcoffout.h [new file with mode: 0644]
contrib/gcc-3.4/include/COPYING [new file with mode: 0644]
contrib/gcc-3.4/include/ansidecl.h [new file with mode: 0644]
contrib/gcc-3.4/include/demangle.h [new file with mode: 0644]
contrib/gcc-3.4/include/dyn-string.h [new file with mode: 0644]
contrib/gcc-3.4/include/fibheap.h [new file with mode: 0644]
contrib/gcc-3.4/include/filenames.h [new file with mode: 0644]
contrib/gcc-3.4/include/hashtab.h [new file with mode: 0644]
contrib/gcc-3.4/include/libiberty.h [new file with mode: 0644]
contrib/gcc-3.4/include/md5.h [new file with mode: 0644]
contrib/gcc-3.4/include/objalloc.h [new file with mode: 0644]
contrib/gcc-3.4/include/obstack.h [new file with mode: 0644]
contrib/gcc-3.4/include/partition.h [new file with mode: 0644]
contrib/gcc-3.4/include/safe-ctype.h [new file with mode: 0644]
contrib/gcc-3.4/include/splay-tree.h [new file with mode: 0644]
contrib/gcc-3.4/libiberty/COPYING.LIB [new file with mode: 0644]
contrib/gcc-3.4/libiberty/ChangeLog [new file with mode: 0644]
contrib/gcc-3.4/libiberty/README [new file with mode: 0644]
contrib/gcc-3.4/libiberty/choose-temp.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/concat.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/cp-demangle.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/cp-demangle.h [new file with mode: 0644]
contrib/gcc-3.4/libiberty/cplus-dem.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/dyn-string.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/fibheap.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/getpwd.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/getruntime.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/hashtab.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/hex.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/insque.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/lbasename.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/lrealpath.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/make-relative-prefix.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/make-temp-file.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/md5.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/objalloc.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/obstack.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/obstacks.texi [new file with mode: 0644]
contrib/gcc-3.4/libiberty/pex-common.h [new file with mode: 0644]
contrib/gcc-3.4/libiberty/pex-unix.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/physmem.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/safe-ctype.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/splay-tree.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/xatexit.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/xexit.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/xmalloc.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/xmemdup.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/xstrdup.c [new file with mode: 0644]
contrib/gcc-3.4/libiberty/xstrerror.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/ChangeLog [new file with mode: 0644]
contrib/gcc-3.4/libobjc/NXConstStr.m [new file with mode: 0644]
contrib/gcc-3.4/libobjc/Object.m [new file with mode: 0644]
contrib/gcc-3.4/libobjc/Protocol.m [new file with mode: 0644]
contrib/gcc-3.4/libobjc/README [new file with mode: 0644]
contrib/gcc-3.4/libobjc/README.threads [new file with mode: 0644]
contrib/gcc-3.4/libobjc/THREADS [new file with mode: 0644]
contrib/gcc-3.4/libobjc/THREADS.MACH [new file with mode: 0644]
contrib/gcc-3.4/libobjc/archive.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/class.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/encoding.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/gc.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/hash.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/init.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/libobjc.def [new file with mode: 0644]
contrib/gcc-3.4/libobjc/libobjc_entry.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/linking.m [new file with mode: 0644]
contrib/gcc-3.4/libobjc/misc.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/nil_method.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/NXConstStr.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/Object.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/Protocol.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/encoding.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/hash.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/objc-api.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/objc-list.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/objc.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/runtime.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/sarray.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/thr.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objc/typedstream.h [new file with mode: 0644]
contrib/gcc-3.4/libobjc/objects.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/sarray.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/selector.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/sendmsg.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/thr-dce.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/thr-objc.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/thr-posix.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/thr-pthreads.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/thr-single.c [new file with mode: 0644]
contrib/gcc-3.4/libobjc/thr.c [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/ChangeLog [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/ChangeLog-2000 [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/ChangeLog-2001 [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/ChangeLog-2002 [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/ChangeLog-2003 [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/README [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/allocator/bitmap_allocator_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/allocator/malloc_allocator_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/allocator/mt_allocator_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/allocator/new_allocator_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/allocator/pool_allocator_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/cpu/generic/atomic_word.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/cpu/generic/atomicity.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/cpu/i386/atomicity.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/cpu/i486/atomicity.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/io/basic_file_stdio.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/io/basic_file_stdio.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/io/c_io_stdio.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/linker-map.dummy [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/linker-map.gnu [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/c++locale_internal.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/c_locale.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/c_locale.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/codecvt_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/codecvt_specializations.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/collate_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/ctype_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/messages_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/messages_members.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/monetary_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/numeric_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/time_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/generic/time_members.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/ieee_1003.1-2001/c_locale.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/ieee_1003.1-2001/c_locale.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/ieee_1003.1-2001/codecvt_specializations.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/ieee_1003.1-2001/messages_members.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/locale/ieee_1003.1-2001/messages_members.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/freebsd/ctype_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/freebsd/ctype_inline.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/freebsd/ctype_noninline.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/freebsd/os_defines.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/netbsd/ctype_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/netbsd/ctype_inline.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/netbsd/ctype_noninline.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/bsd/netbsd/os_defines.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/generic/ctype_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/generic/ctype_inline.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/generic/ctype_noninline.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/config/os/generic/os_defines.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/Makefile.am [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/Makefile.in [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/algo.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/algobase.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/alloc.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/backward_warning.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/bvector.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/complex.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/defalloc.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/deque.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/fstream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/function.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/hash_map.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/hash_set.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/hashtable.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/heap.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/iomanip.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/iostream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/istream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/iterator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/list.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/map.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/multimap.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/multiset.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/new.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/ostream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/pair.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/queue.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/rope.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/set.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/slist.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/stack.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/stream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/streambuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/strstream [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/tempbuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/tree.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/backward/vector.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/allocator_traits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/atomicity.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/basic_ios.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/basic_ios.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/basic_string.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/basic_string.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/boost_concept_check.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/c++config [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/char_traits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/codecvt.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/concept_check.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/concurrence.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/cpp_type_traits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/deque.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/fstream.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/functexcept.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/gslice.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/gslice_array.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/indirect_array.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/ios_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/istream.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/list.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/locale_classes.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/locale_facets.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/locale_facets.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/localefwd.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/mask_array.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/ostream.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/postypes.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/slice_array.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/sstream.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_algo.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_algobase.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_bvector.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_construct.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_deque.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_function.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_heap.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_iterator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_iterator_base_funcs.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_iterator_base_types.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_list.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_map.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_multimap.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_multiset.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_numeric.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_pair.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_queue.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_raw_storage_iter.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_relops.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_set.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_stack.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_tempbuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_threads.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_tree.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_uninitialized.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stl_vector.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stream_iterator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/streambuf.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/streambuf_iterator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/stringfwd.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/type_traits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/valarray_after.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/valarray_array.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/valarray_array.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/valarray_before.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/bits/vector.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cassert.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cctype.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cerrno.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cfloat.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_ciso646.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_climits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_clocale.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cmath.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_csetjmp.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_csignal.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cstdarg.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cstddef.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cstdio.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cstdlib.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cstring.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_ctime.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cwchar.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c/std_cwctype.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/assert.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/ctype.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/errno.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/float.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/iso646.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/limits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/locale.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/math.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/setjmp.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/signal.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/stdarg.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/stddef.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/stdio.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/stdlib.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/string.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/time.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/wchar.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_compatibility/wctype.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/cmath.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cassert.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cctype.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cerrno.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cfloat.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_ciso646.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_climits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_clocale.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cmath.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_csetjmp.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_csignal.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cstdarg.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cstddef.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cstdio.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cstdlib.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cstring.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_ctime.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cwchar.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/c_std/std_cwctype.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/bitset [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/debug.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/deque [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/formatter.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/hash_map [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/hash_map.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/hash_multimap.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/hash_multiset.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/hash_set [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/hash_set.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/list [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/map [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/map.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/multimap.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/multiset.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/safe_base.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/safe_iterator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/safe_iterator.tcc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/safe_sequence.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/set [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/set.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/string [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/debug/vector [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/algorithm [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/bitmap_allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/debug_allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/demangle.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/enc_filebuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/functional [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/hash_fun.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/hash_map [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/hash_set [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/hashtable.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/iterator [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/malloc_allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/memory [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/mt_allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/new_allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/numeric [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/pod_char_traits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/pool_allocator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/rb_tree [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/rope [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/ropeimpl.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/slist [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/stdio_filebuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/ext/stdio_sync_filebuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_algorithm.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_bitset.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_complex.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_deque.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_fstream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_functional.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_iomanip.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_ios.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_iosfwd.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_iostream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_istream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_iterator.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_limits.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_list.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_locale.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_map.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_memory.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_numeric.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_ostream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_queue.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_set.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_sstream.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_stack.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_stdexcept.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_streambuf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_string.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_utility.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_valarray.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/std/std_vector.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/include/stdc++.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libmath/copysignf.c [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libmath/mathconf.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libmath/signbit.c [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libmath/signbitf.c [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libmath/signbitl.c [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libmath/stubs.c [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/cxxabi.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/del_op.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/del_opnt.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/del_opv.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/del_opvnt.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_alloc.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_aux_runtime.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_catch.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_exception.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_globals.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_personality.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_term_handler.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_terminate.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_throw.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_type.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/eh_unex_handler.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/exception [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/exception_defines.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/guard.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/new [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/new_handler.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/new_op.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/new_opnt.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/new_opv.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/new_opvnt.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/pure.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/tinfo.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/tinfo.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/tinfo2.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/typeinfo [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/unwind-cxx.h [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/vec.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/libsupc++/vterminate.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/allocator-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/allocator.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/codecvt.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/complex_io.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/concept-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ctype.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/debug.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/debug_list.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ext-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/fstream-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/functexcept.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/globals_io.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/globals_locale.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/io-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ios.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ios_failure.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ios_init.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ios_locale.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/istream-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/limits.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/list.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/locale-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/locale-misc-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/locale.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/locale_facets.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/locale_init.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/localename.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/misc-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/ostream-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/sstream-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/stdexcept.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/streambuf-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/string-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/strstream.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/tree.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/valarray-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/wlocale-inst.cc [new file with mode: 0644]
contrib/gcc-3.4/libstdc++-v3/src/wstring-inst.cc [new file with mode: 0644]

diff --git a/contrib/gcc-3.4/BUGS b/contrib/gcc-3.4/BUGS
new file mode 100644 (file)
index 0000000..05d7210
--- /dev/null
@@ -0,0 +1,809 @@
+
+                                   GCC Bugs
+
+   The   latest   version   of  this  document  is  always  available  at
+   [1]http://gcc.gnu.org/bugs.html.
+     _________________________________________________________________
+
+Table of Contents
+
+     * [2]Reporting Bugs
+          + [3]What we need
+          + [4]What we DON'T want
+          + [5]Where to post it
+          + [6]Detailed bug reporting instructions
+          + [7]Detailed bug reporting instructions for GNAT
+          + [8]Detailed   bug   reporting   instructions   when  using  a
+            precompiled header
+     * [9]Frequently Reported Bugs in GCC
+          + [10]C++
+               o [11]Missing features
+               o [12]Bugs fixed in the 3.4 series
+          + [13]Fortran
+     * [14]Non-bugs
+          + [15]General
+          + [16]C
+          + [17]C++
+               o [18]Common problems when upgrading the compiler
+     _________________________________________________________________
+
+                                Reporting Bugs
+
+   The  main  purpose of a bug report is to enable us to fix the bug. The
+   most  important  prerequisite  for  this  is  that  the report must be
+   complete and self-contained, which we explain in detail below.
+
+   Before  you report a bug, please check the [19]list of well-known bugs
+   and,  if  possible  in any way, try a current development snapshot. If
+   you  want  to report a bug with versions of GCC before 3.1 we strongly
+   recommend upgrading to the current release first.
+
+   Before  reporting  that  GCC  compiles  your  code incorrectly, please
+   compile  it  with  gcc -Wall and see whether this shows anything wrong
+   with your code that could be the cause instead of a bug in GCC.
+
+Summarized bug reporting instructions
+
+   After  this  summary, you'll find detailed bug reporting instructions,
+   that  explain  how to obtain some of the information requested in this
+   summary.
+
+  What we need
+
+   Please  include  in  your  bug  report all of the following items, the
+   first three of which can be obtained from the output of gcc -v:
+     * the exact version of GCC;
+     * the system type;
+     * the options given when GCC was configured/built;
+     * the complete command line that triggers the bug;
+     * the compiler output (error messages, warnings, etc.); and
+     * the  preprocessed  file (*.i*) that triggers the bug, generated by
+       adding -save-temps to the complete compilation command, or, in the
+       case  of  a  bug  report for the GNAT front end, a complete set of
+       source files (see below).
+
+  What we do not want
+
+     * A source file that #includes header files that are left out of the
+       bug report (see above)
+     * That source file and a collection of header files.
+     * An  attached archive (tar, zip, shar, whatever) containing all (or
+       some :-) of the above.
+     * A  code snippet that won't cause the compiler to produce the exact
+       output  mentioned  in  the bug report (e.g., a snippet with just a
+       few  lines  around  the one that apparently triggers the bug, with
+       some   pieces   replaced  with  ellipses  or  comments  for  extra
+       obfuscation :-)
+     * The  location  (URL) of the package that failed to build (we won't
+       download it, anyway, since you've already given us what we need to
+       duplicate the bug, haven't you? :-)
+     * An  error  that  occurs  only  some of the times a certain file is
+       compiled,  such that retrying a sufficient number of times results
+       in  a  successful  compilation;  this  is  a symptom of a hardware
+       problem, not of a compiler bug (sorry)
+     * E-mail  messages that complement previous, incomplete bug reports.
+       Post  a  new, self-contained, full bug report instead, if possible
+       as a follow-up to the original bug report
+     * Assembly  files  (*.s)  produced  by  the  compiler, or any binary
+       files,   such   as  object  files,  executables,  core  files,  or
+       precompiled header files
+     * Duplicate  bug  reports,  or  reports of bugs already fixed in the
+       development tree, especially those that have already been reported
+       as fixed last week :-)
+     * Bugs  in  the  assembler,  the  linker or the C library. These are
+       separate  projects,  with separate mailing lists and different bug
+       reporting procedures
+     * Bugs  in  releases  or  snapshots  of  GCC  not  issued by the GNU
+       Project. Report them to whoever provided you with the release
+     * Questions  about  the  correctness  or  the  expected  behavior of
+       certain constructs that are not GCC extensions. Ask them in forums
+       dedicated to the discussion of the programming language
+
+  Where to post it
+
+   Please  submit  your  bug report directly to the [20]GCC bug database.
+   Alternatively,  you  can  use  the  gccbug  script that mails your bug
+   report to the bug database.
+   Only  if  all  this  is absolutely impossible, mail all information to
+   [21]gcc-bugs@gcc.gnu.org.
+
+Detailed bug reporting instructions
+
+   Please  refer to the [22]next section when reporting bugs in GNAT, the
+   Ada  compiler,  or  to the [23]one after that when reporting bugs that
+   appear when using a precompiled header.
+
+   In  general, all the information we need can be obtained by collecting
+   the  command  line  below,  as well as its output and the preprocessed
+   file it generates.
+
+     gcc -v -save-temps all-your-options source-file
+
+   Typically  the  preprocessed  file (extension .i for C or .ii for C++,
+   and .f if the preprocessor is used on Fortran files) will be large, so
+   please compress the resulting file with one of the popular compression
+   programs  such as bzip2, gzip, zip or compress (in decreasing order of
+   preference). Use maximum compression (-9) if available. Please include
+   the  compressed  preprocessor  output  in your bug report, even if the
+   source  code  is  freely  available elsewhere; it makes the job of our
+   volunteer testers much easier.
+
+   The  only  excuses  to not send us the preprocessed sources are (i) if
+   you've  found  a  bug  in the preprocessor, (ii) if you've reduced the
+   testcase  to a small file that doesn't include any other file or (iii)
+   if  the  bug appears only when using precompiled headers. If you can't
+   post  the  preprocessed sources because they're proprietary code, then
+   try to create a small file that triggers the same problem.
+
+   Since  we're  supposed  to  be  able  to re-create the assembly output
+   (extension  .s),  you usually should not include it in the bug report,
+   although  you  may want to post parts of it to point out assembly code
+   you consider to be wrong.
+
+   Whether to use MIME attachments or uuencode is up to you. In any case,
+   make  sure  the compiler command line, version and error output are in
+   plain text, so that we don't have to decode the bug report in order to
+   tell  who  should  take  care  of  it. A meaningful subject indicating
+   language and platform also helps.
+
+   Please  avoid  posting  an archive (.tar, .shar or .zip); we generally
+   need   just  a  single  file  to  reproduce  the  bug  (the  .i/.ii/.f
+   preprocessed  file),  and,  by  storing  it in an archive, you're just
+   making our volunteers' jobs harder. Only when your bug report requires
+   multiple source files to be reproduced should you use an archive. This
+   is,  for  example,  the  case  if  you are using INCLUDE directives in
+   Fortran  code,  which  are  not processed by the preprocessor, but the
+   compiler.  In that case, we need the main file and all INCLUDEd files.
+   In  any  case, make sure the compiler version, error message, etc, are
+   included  in  the  body  of  your  bug  report  as plain text, even if
+   needlessly duplicated as part of an archive.
+
+   If  you  fail  to  supply  enough  information  for a bug report to be
+   reproduced,   someone   will  probably  ask  you  to  post  additional
+   information  (or just ignore your bug report, if they're in a bad day,
+   so  try to get it right on the first posting :-). In this case, please
+   post the additional information to the bug reporting mailing list, not
+   just  to  the  person  who requested it, unless explicitly told so. If
+   possible, please include in this follow-up all the information you had
+   supplied  in  the  incomplete  bug  report (including the preprocessor
+   output), so that the new bug report is self-contained.
+
+Detailed bug reporting instructions for GNAT
+
+   See  the  [24]previous  section for bug reporting instructions for GCC
+   language implementations other than Ada.
+
+   Bug  reports  have  to  contain  at least the following information in
+   order to be useful:
+     * the exact version of GCC, as shown by "gcc -v";
+     * the system type;
+     * the options when GCC was configured/built;
+     * the  exact  command  line passed to the gcc program triggering the
+       bug  (not  just  the flags passed to gnatmake, but gnatmake prints
+       the parameters it passed to gcc)
+     * a collection of source files for reproducing the bug, preferably a
+       minimal set (see below);
+     * a description of the expected behavior;
+     * a description of actual behavior.
+
+   If  your  code  depends  on  additional  source files (usually package
+   specifications), submit the source code for these compilation units in
+   a  single  file that is acceptable input to gnatchop, i.e. contains no
+   non-Ada  text. If the compilation terminated normally, you can usually
+   obtain a list of dependencies using the "gnatls -d main_unit" command,
+   where  main_unit  is the file name of the main compilation unit (which
+   is also passed to gcc).
+
+   If  you  report  a  bug  which causes the compiler to print a bug box,
+   include that bug box in your report, and do not forget to send all the
+   source files listed after the bug box along with your report.
+
+   If  you  use gnatprep, be sure to send in preprocessed sources (unless
+   you have to report a bug in gnatprep).
+
+   When  you  have  checked that your report meets these criteria, please
+   submit  it  according  to  our [25]generic instructions. (If you use a
+   mailing  list  for  reporting,  please  include  an "[Ada]" tag in the
+   subject.)
+
+Detailed bug reporting instructions when using a precompiled header
+
+   If  you're  encountering  a  bug  when using a precompiled header, the
+   first thing to do is to delete the precompiled header, and try running
+   the  same GCC command again. If the bug happens again, the bug doesn't
+   really  involve  precompiled  headers,  please report it without using
+   them by following the instructions [26]above.
+
+   If  you've  found  a  bug  while  building  a  precompiled header (for
+   instance,   the  compiler  crashes),  follow  the  usual  instructions
+   [27]above.
+
+   If  you've  found  a  real  precompiled header bug, what we'll need to
+   reproduce  it  is  the  sources  to build the precompiled header (as a
+   single .i file), the source file that uses the precompiled header, any
+   other  headers  that  source file includes, and the command lines that
+   you used to build the precompiled header and to use it.
+
+   Please don't send us the actual precompiled header. It is likely to be
+   very large and we can't use it to reproduce the problem.
+     _________________________________________________________________
+
+                        Frequently Reported Bugs in GCC
+
+   This  is  a  list of bugs in GCC that are reported very often, but not
+   yet  fixed.  While  it  is  certainly  better  to  fix bugs instead of
+   documenting  them,  this  document  might  save  people  the effort of
+   writing a bug report when the bug is already well-known.
+
+   There  are many reasons why a reported bug doesn't get fixed. It might
+   be  difficult  to  fix, or fixing it might break compatibility. Often,
+   reports  get  a  low  priority  when there is a simple work-around. In
+   particular, bugs caused by invalid code have a simple work-around: fix
+   the code.
+     _________________________________________________________________
+
+C++
+
+  Missing features
+
+   The export keyword is not implemented.
+          Most  C++ compilers (G++ included) do not yet implement export,
+          which   is  necessary  for  separate  compilation  of  template
+          declarations   and  definitions.  Without  export,  a  template
+          definition  must be in scope to be used. The obvious workaround
+          is  simply  to  place  all  definitions  in  the header itself.
+          Alternatively,   the   compilation   unit  containing  template
+          definitions may be included from the header.
+
+  Bugs fixed in the 3.4 series
+
+   The  following  bugs are present up to (and including) GCC 3.3.x. They
+   have been fixed in 3.4.0.
+
+   Two-stage name-lookup.
+          GCC   did   not   implement  two-stage  name-lookup  (also  see
+          [28]below).
+
+   Covariant return types.
+          GCC did not implement non-trivial covariant returns.
+
+   Parse errors for "simple" code.
+          GCC gave parse errors for seemingly simple code, such as
+
+struct A
+{
+  A();
+  A(int);
+};
+
+struct B
+{
+  B(A);
+  B(A,A);
+  void foo();
+};
+
+A bar()
+{
+  B b(A(),A(1));  // Variable b, initialized with two temporaries
+  B(A(2)).foo();  // B temporary, initialized with A temporary
+  return (A());   // return A temporary
+}
+
+          Although  being  valid  code,  each  of  the three lines with a
+          comment  was  rejected  by  GCC.  The  work-arounds  for  older
+          compiler versions proposed below do not change the semantics of
+          the programs at all.
+
+          The problem in the first case was that GCC started to parse the
+          declaration  of  b as a function called b returning B, taking a
+          function returning A as an argument. When it encountered the 1,
+          it  was  too  late.  To  show  the compiler that this should be
+          really  an  expression,  a comma operator with a dummy argument
+          could be used:
+
+B b((0,A()),A(1));
+
+          The  work-around  for  simpler cases like the second one was to
+          add  additional  parentheses  around  the expressions that were
+          mistaken as declarations:
+
+(B(A(2))).foo();
+
+          In the third case, however, additional parentheses were causing
+          the  problems:  The  compiler  interpreted  A()  as  a function
+          (taking no arguments, returning A), and (A()) as a cast lacking
+          an  expression  to  be  casted,  hence  the  parse  error.  The
+          work-around was to omit the parentheses:
+
+return A();
+
+          This  problem  occured  in  a  number  of  variants;  in  throw
+          statements,   people   also   frequently   put  the  object  in
+          parentheses.
+     _________________________________________________________________
+
+Fortran
+
+   Fortran  bugs  are documented in the G77 manual rather than explicitly
+   listed  here.  Please see [29]Known Causes of Trouble with GNU Fortran
+   in the G77 manual.
+     _________________________________________________________________
+
+                                   Non-bugs
+
+   The  following are not actually bugs, but are reported often enough to
+   warrant a mention here.
+
+   It  is  not  always a bug in the compiler, if code which "worked" in a
+   previous  version,  is now rejected. Earlier versions of GCC sometimes
+   were less picky about standard conformance and accepted invalid source
+   code.  In addition, programming languages themselves change, rendering
+   code  invalid  that  used  to be conforming (this holds especially for
+   C++).  In  either  case,  you  should update your code to match recent
+   language standards.
+     _________________________________________________________________
+
+General
+
+   Problems with floating point numbers - the [30]most often reported
+          non-bug.
+          In  a  number  of  cases, GCC appears to perform floating point
+          computations incorrectly. For example, the C++ program
+
+#include <iostream>
+
+int main()
+{
+  double a = 0.5;
+  double b = 0.01;
+  std::cout << (int)(a / b) << std::endl;
+  return 0;
+}
+
+          might  print 50 on some systems and optimization levels, and 49
+          on others.
+
+          This  is  the result of rounding: The computer cannot represent
+          all real numbers exactly, so it has to use approximations. When
+          computing  with  approximation,  the computer needs to round to
+          the nearest representable number.
+
+          This  is  not a bug in the compiler, but an inherent limitation
+          of  the  floating  point types. Please study [31]this paper for
+          more information.
+     _________________________________________________________________
+
+C
+
+   Casting does not work as expected when optimization is turned on.
+          This  is  often  caused by a violation of aliasing rules, which
+          are  part of the ISO C standard. These rules say that a program
+          is invalid if you try to access a variable through a pointer of
+          an  incompatible  type.  This  is  happening  in  the following
+          example  where a short is accessed through a pointer to integer
+          (the code assumes 16-bit shorts and 32-bit ints):
+
+#include <stdio.h>
+
+int main()
+{
+  short a[2];
+
+  a[0]=0x1111;
+  a[1]=0x1111;
+
+  *(int *)a = 0x22222222; /* violation of aliasing rules */
+
+  printf("%x %x\n", a[0], a[1]);
+  return 0;
+}
+
+          The  aliasing  rules  were  designed  to  allow  compilers more
+          aggressive  optimization. Basically, a compiler can assume that
+          all  changes to variables happen through pointers or references
+          to  variables  of  a  type compatible to the accessed variable.
+          Dereferencing  a  pointer  that  violates  the  aliasing  rules
+          results in undefined behavior.
+
+          In  the  case  above,  the  compiler  may assume that no access
+          through  an  integer pointer can change the array a, consisting
+          of  shorts. Thus, printf may be called with the original values
+          of a[0] and a[1]. What really happens is up to the compiler and
+          may change with architecture and optimization level.
+
+          Recent  versions  of  GCC  turn on the option -fstrict-aliasing
+          (which  allows  alias-based optimizations) by default with -O2.
+          And some architectures then really print "1111 1111" as result.
+          Without   optimization   the   executable   will  generate  the
+          "expected" output "2222 2222".
+
+          To  disable  optimizations  based  on alias-analysis for faulty
+          legacy  code,  the option -fno-strict-aliasing can be used as a
+          work-around.
+
+          The option -Wstrict-aliasing (which is included in -Wall) warns
+          about some - but not all - cases of violation of aliasing rules
+          when -fstrict-aliasing is active.
+
+          To  fix  the  code above, you can use a union instead of a cast
+          (note  that  this  is a GCC extension which might not work with
+          other compilers):
+
+#include <stdio.h>
+
+int main()
+{
+  union
+  {
+    short a[2];
+    int i;
+  } u;
+
+  u.a[0]=0x1111;
+  u.a[1]=0x1111;
+
+  u.i = 0x22222222;
+
+  printf("%x %x\n", u.a[0], u.a[1]);
+  return 0;
+}
+
+          Now the result will always be "2222 2222".
+
+          For  some  more insight into the subject, please have a look at
+          [32]this article.
+
+   Cannot use preprocessor directive in macro arguments.
+          Let  me  guess...  you  used an older version of GCC to compile
+          code that looks something like this:
+
+  memcpy(dest, src,
+#ifdef PLATFORM1
+         12
+#else
+         24
+#endif
+        );
+
+          and you got a whole pile of error messages:
+
+test.c:11: warning: preprocessing directive not recognized within macro arg
+test.c:11: warning: preprocessing directive not recognized within macro arg
+test.c:11: warning: preprocessing directive not recognized within macro arg
+test.c: In function `foo':
+test.c:6: undefined or invalid # directive
+test.c:8: undefined or invalid # directive
+test.c:9: parse error before `24'
+test.c:10: undefined or invalid # directive
+
+          This  is  because your C library's <string.h> happens to define
+          memcpy  as  a  macro - which is perfectly legitimate. In recent
+          versions of glibc, for example, printf is among those functions
+          which are implemented as macros.
+
+          Versions  of  GCC  prior to 3.3 did not allow you to put #ifdef
+          (or any other preprocessor directive) inside the arguments of a
+          macro. The code therefore would not compile.
+
+          As of GCC 3.3 this kind of construct is always accepted and the
+          preprocessor  will  probably  do  what  you expect, but see the
+          manual for detailed semantics.
+
+          However,  this  kind  of code is not portable. It is "undefined
+          behavior"  according  to  the  C standard; that means different
+          compilers  may  do  different  things  with  it.  It  is always
+          possible  to rewrite code which uses conditionals inside macros
+          so that it doesn't. You could write the above example
+
+#ifdef PLATFORM1
+   memcpy(dest, src, 12);
+#else
+   memcpy(dest, src, 24);
+#endif
+
+          This  is  a bit more typing, but I personally think it's better
+          style in addition to being more portable.
+
+   Cannot initialize a static variable with stdin.
+          This  has  nothing to do with GCC, but people ask us about it a
+          lot. Code like this:
+
+#include <stdio.h>
+
+FILE *yyin = stdin;
+
+          will  not  compile  with  GNU  libc,  because  stdin  is  not a
+          constant.  This  was  done  deliberately,  to make it easier to
+          maintain  binary  compatibility  when the type FILE needs to be
+          changed. It is surprising for people used to traditional Unix C
+          libraries, but it is permitted by the C standard.
+
+          This  construct  commonly  occurs  in  code  generated  by  old
+          versions  of  lex  or yacc. We suggest you try regenerating the
+          parser  with  a current version of flex or bison, respectively.
+          In   your  own  code,  the  appropriate  fix  is  to  move  the
+          initialization to the beginning of main.
+
+          There  is  a  common  misconception that the GCC developers are
+          responsible  for  GNU  libc.  These  are  in  fact two entirely
+          separate  projects; please check the [33]GNU libc web pages for
+          details.
+     _________________________________________________________________
+
+C++
+
+   Nested classes can access private members and types of the containing
+          class.
+          Defect  report  45 clarifies that nested classes are members of
+          the  class  they  are  nested  in, and so are granted access to
+          private members of that class.
+
+   G++ emits two copies of constructors and destructors.
+          In   general   there  are  three  types  of  constructors  (and
+          destructors).
+
+         1. The complete object constructor/destructor.
+         2. The base object constructor/destructor.
+         3. The allocating constructor/deallocating destructor.
+
+          The  first  two  are  different,  when virtual base classes are
+          involved.
+
+   Global destructors are not run in the correct order.
+          Global  destructors should be run in the reverse order of their
+          constructors  completing. In most cases this is the same as the
+          reverse  order  of  constructors  starting, but sometimes it is
+          different,  and that is important. You need to compile and link
+          your  programs  with  --use-cxa-atexit. We have not turned this
+          switch  on  by  default,  as  it  requires  a cxa aware runtime
+          library (libc, glibc, or equivalent).
+
+   Classes in exception specifiers must be complete types.
+          [15.4]/1  tells you that you cannot have an incomplete type, or
+          pointer  to  incomplete  (other than cv void *) in an exception
+          specification.
+
+   Exceptions don't work in multithreaded applications.
+          You  need  to  rebuild g++ and libstdc++ with --enable-threads.
+          Remember,  C++ exceptions are not like hardware interrupts. You
+          cannot  throw  an  exception  in  one  thread  and  catch it in
+          another.  You  cannot  throw an exception from a signal handler
+          and catch it in the main thread.
+
+   Templates, scoping, and digraphs.
+          If  you  have a class in the global namespace, say named X, and
+          want to give it as a template argument to some other class, say
+          std::vector, then std::vector<::X> fails with a parser error.
+
+          The  reason  is that the standard mandates that the sequence <:
+          is  treated  as if it were the token [. (There are several such
+          combinations   of  characters  -  they  are  called  digraphs.)
+          Depending  on  the  version,  the compiler then reports a parse
+          error  before the character : (the colon before X) or a missing
+          closing bracket ].
+
+          The  simplest  way to avoid this is to write std::vector< ::X>,
+          i.e.  place  a  space between the opening angle bracket and the
+          scope operator.
+
+   Copy constructor access check while initializing a reference.
+          Consider this code:
+
+class A
+{
+public:
+  A();
+
+private:
+  A(const A&);   // private copy ctor
+};
+
+A makeA(void);
+void foo(const A&);
+
+void bar(void)
+{
+  foo(A());       // error, copy ctor is not accessible
+  foo(makeA());   // error, copy ctor is not accessible
+
+  A a1;
+  foo(a1);        // OK, a1 is a lvalue
+}
+
+          Starting with GCC 3.4.0, binding an rvalue to a const reference
+          requires   an   accessible  copy  constructor.  This  might  be
+          surprising  at  first  sight,  especially  since  most  popular
+          compilers do not correctly implement this rule.
+
+          The C++ Standard says that a temporary object should be created
+          in  this  context  and  its  contents filled with a copy of the
+          object  we  are  trying  to bind to the reference; it also says
+          that  the  temporary  copy  can  be  elided,  but  the semantic
+          constraints  (eg.  accessibility) of the copy constructor still
+          have to be checked.
+
+          For   further   information,  you  can  consult  the  following
+          paragraphs  of  the  C++  standard: [dcl.init.ref]/5, bullet 2,
+          sub-bullet 1, and [class.temporary]/2.
+
+  Common problems when upgrading the compiler
+
+    ABI changes
+
+   The C++ application binary interface (ABI) consists of two components:
+   the  first  defines  how  the  elements  of  classes are laid out, how
+   functions  are called, how function names are mangled, etc; the second
+   part deals with the internals of the objects in libstdc++. Although we
+   strive  for  a  non-changing ABI, so far we have had to modify it with
+   each  major  release. If you change your compiler to a different major
+   release you must recompile all libraries that contain C++ code. If you
+   fail  to  do  so  you  risk  getting  linker  errors or malfunctioning
+   programs. Some of our Java support libraries also contain C++ code, so
+   you might want to recompile all libraries to be safe. It should not be
+   necessary to recompile if you have changed to a bug-fix release of the
+   same  version  of  the compiler; bug-fix releases are careful to avoid
+   ABI changes. See also the [34]compatibility section of the GCC manual.
+
+   Remark:  A  major  release  is  designated by a change to the first or
+   second  component  of  the  two- or three-part version number. A minor
+   (bug-fix)  release  is  designated  by a change to the third component
+   only.  Thus  GCC 3.2 and 3.3 are major releases, while 3.3.1 and 3.3.2
+   are  bug-fix  releases  for  GCC  3.3.  With  the  3.4  series  we are
+   introducing  a  new naming scheme; the first release of this series is
+   3.4.0 instead of just 3.4.
+
+    Standard conformance
+
+   With  each  release,  we try to make G++ conform closer to the ISO C++
+   standard  (available  at  [35]http://www.ncits.org/cplusplus.htm).  We
+   have  also  implemented  some  of  the core and library defect reports
+   (available at
+   [36]http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html     &
+   [37]http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html
+   respectively).
+
+   Non-conforming  legacy code that worked with older versions of GCC may
+   be  rejected by more recent compilers. There is no command-line switch
+   to   ensure   compatibility   in  general,  because  trying  to  parse
+   standard-conforming  and  old-style code at the same time would render
+   the   C++   frontend   unmaintainable.  However,  some  non-conforming
+   constructs  are  allowed  when the command-line option -fpermissive is
+   used.
+
+   Two  milestones in standard conformance are GCC 3.0 (including a major
+   overhaul  of the standard library) and the 3.4.0 version (with its new
+   C++ parser).
+
+    New in GCC 3.0
+
+     * The  standard  library is much more conformant, and uses the std::
+       namespace (which is now a real namespace, not an alias for ::).
+     * The standard header files for the c library don't end with .h, but
+       begin with c (i.e. <cstdlib> rather than <stdlib.h>). The .h names
+       are still available, but are deprecated.
+     * <strstream> is deprecated, use <sstream> instead.
+     * streambuf::seekoff  &  streambuf::seekpos are private, instead use
+       streambuf::pubseekoff & streambuf::pubseekpos respectively.
+     * If std::operator << (std::ostream &, long long) doesn't exist, you
+       need to recompile libstdc++ with --enable-long-long.
+
+   If  you  get  lots  of  errors about things like cout not being found,
+   you've most likely forgotten to tell the compiler to look in the std::
+   namespace. There are several ways to do this:
+     * Say std::cout at the call. This is the most explicit way of saying
+       what you mean.
+     * Say  using  std::cout; somewhere before the call. You will need to
+       do  this  for  each  function  or  type  you  wish to use from the
+       standard library.
+     * Say  using  namespace  std; somewhere before the call. This is the
+       quick-but-dirty  fix. This brings the whole of the std:: namespace
+       into  scope. Never do this in a header file, as every user of your
+       header file will be affected by this decision.
+
+    New in GCC 3.4.0
+
+   The  new  parser  brings  a lot of improvements, especially concerning
+   name-lookup.
+     * The  "implicit  typename"  extension  got  removed (it was already
+       deprecated  since  GCC  3.1),  so  that  the following code is now
+       rejected, see [14.6]:
+
+template <typename> struct A
+{
+    typedef int X;
+};
+
+template <typename T> struct B
+{
+    A<T>::X          x;  // error
+    typename A<T>::X y;  // OK
+};
+
+B<void> b;
+
+     * For  similar reasons, the following code now requires the template
+       keyword, see [14.2]:
+
+template <typename> struct A
+{
+    template <int> struct X {};
+};
+
+template <typename T> struct B
+{
+    typename A<T>::X<0>          x;  // error
+    typename A<T>::template X<0> y;  // OK
+};
+
+B<void> b;
+
+     * We  now  have two-stage name-lookup, so that the following code is
+       rejected, see [14.6]/9:
+
+template <typename T> int foo()
+{
+    return i;  // error
+}
+
+     * This also affects members of base classes, see [14.6.2]:
+
+template <typename> struct A
+{
+    int i, j;
+};
+
+template <typename T> struct B : A<T>
+{
+    int foo1() { return i; }       // error
+    int foo2() { return this->i; } // OK
+    int foo3() { return B<T>::i; } // OK
+    int foo4() { return A<T>::i; } // OK
+
+    using A<T>::j;
+    int foo5() { return j; }       // OK
+};
+
+   In  addition  to  the  problems  listed  above,  the manual contains a
+   section on [38]Common Misunderstandings with GNU C++.
+
+References
+
+   1. http://gcc.gnu.org/bugs.html
+   2. http://gcc.gnu.org/bugs.html#report
+   3. http://gcc.gnu.org/bugs.html#need
+   4. http://gcc.gnu.org/bugs.html#dontwant
+   5. http://gcc.gnu.org/bugs.html#where
+   6. http://gcc.gnu.org/bugs.html#detailed
+   7. http://gcc.gnu.org/bugs.html#gnat
+   8. http://gcc.gnu.org/bugs.html#pch
+   9. http://gcc.gnu.org/bugs.html#known
+  10. http://gcc.gnu.org/bugs.html#cxx
+  11. http://gcc.gnu.org/bugs.html#missing
+  12. http://gcc.gnu.org/bugs.html#fixed34
+  13. http://gcc.gnu.org/bugs.html#fortran
+  14. http://gcc.gnu.org/bugs.html#nonbugs
+  15. http://gcc.gnu.org/bugs.html#nonbugs_general
+  16. http://gcc.gnu.org/bugs.html#nonbugs_c
+  17. http://gcc.gnu.org/bugs.html#nonbugs_cxx
+  18. http://gcc.gnu.org/bugs.html#upgrading
+  19. http://gcc.gnu.org/bugs.html#known
+  20. http://gcc.gnu.org/bugzilla/
+  21. mailto:gcc-bugs@gcc.gnu.org
+  22. http://gcc.gnu.org/bugs.html#gnat
+  23. http://gcc.gnu.org/bugs.html#pch
+  24. http://gcc.gnu.org/bugs.html#detailed
+  25. http://gcc.gnu.org/bugs.html#where
+  26. http://gcc.gnu.org/bugs.html#detailed
+  27. http://gcc.gnu.org/bugs.html#detailed
+  28. http://gcc.gnu.org/bugs.html#new34
+  29. http://gcc.gnu.org/onlinedocs/g77/Trouble.html
+  30. http://gcc.gnu.org/PR323
+  31. http://www.validlab.com/goldberg/paper.ps
+  32. http://mail-index.NetBSD.org/tech-kern/2003/08/11/0001.html
+  33. http://www.gnu.org/software/libc/
+  34. http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html
+  35. http://www.ncits.org/cplusplus.htm
+  36. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html
+  37. http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html
+  38. http://gcc.gnu.org/onlinedocs/gcc/C---Misunderstandings.html
diff --git a/contrib/gcc-3.4/COPYING b/contrib/gcc-3.4/COPYING
new file mode 100644 (file)
index 0000000..d60c31a
--- /dev/null
@@ -0,0 +1,340 @@
+                   GNU GENERAL PUBLIC LICENSE
+                      Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                           Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+\f
+                   GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+\f
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+\f
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+\f
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                           NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                    END OF TERMS AND CONDITIONS
+\f
+           How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/contrib/gcc-3.4/COPYING.LIB b/contrib/gcc-3.4/COPYING.LIB
new file mode 100644 (file)
index 0000000..b1e3f5a
--- /dev/null
@@ -0,0 +1,504 @@
+                 GNU LESSER GENERAL PUBLIC LICENSE
+                      Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+                           Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+  This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+not price.  Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+  To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+\f
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License.  This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom.  The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+of an advantage over competing non-free programs.  These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries.  However, the Lesser license provides advantages in certain
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+\f
+                 GNU LESSER GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+  
+  1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+  You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+\f
+  2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library.  To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License.  (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+\f
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+  If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library".  Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+  However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library".  The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+  When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library.  The
+threshold for this to be true is not precisely defined by law.
+
+  If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work.  (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+  Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+\f
+  6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+  You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License.  You must supply a copy of this License.  If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License.  Also, you must do one
+of these things:
+
+    a) Accompany the work with the complete corresponding
+    machine-readable source code for the Library including whatever
+    changes were used in the work (which must be distributed under
+    Sections 1 and 2 above); and, if the work is an executable linked
+    with the Library, with the complete machine-readable "work that
+    uses the Library", as object code and/or source code, so that the
+    user can modify the Library and then relink to produce a modified
+    executable containing the modified Library.  (It is understood
+    that the user who changes the contents of definitions files in the
+    Library will not necessarily be able to recompile the application
+    to use the modified definitions.)
+
+    b) Use a suitable shared library mechanism for linking with the
+    Library.  A suitable mechanism is one that (1) uses at run time a
+    copy of the library already present on the user's computer system,
+    rather than copying library functions into the executable, and (2)
+    will operate properly with a modified version of the library, if
+    the user installs one, as long as the modified version is
+    interface-compatible with the version that the work was made with.
+
+    c) Accompany the work with a written offer, valid for at
+    least three years, to give the same user the materials
+    specified in Subsection 6a, above, for a charge no more
+    than the cost of performing this distribution.
+
+    d) If distribution of the work is made by offering access to copy
+    from a designated place, offer equivalent access to copy the above
+    specified materials from the same place.
+
+    e) Verify that the user has already received a copy of these
+    materials or that you have already sent this user a copy.
+
+  For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it.  However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+  It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system.  Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+\f
+  7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+    a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    facilities.  This must be distributed under the terms of the
+    Sections above.
+
+    b) Give prominent notice with the combined library of the fact
+    that part of it is a work based on the Library, and explaining
+    where to find the accompanying uncombined form of the same work.
+
+  8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License.  Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License.  However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+  9. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Library or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+  10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+\f
+  11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded.  In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+  13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation.  If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+\f
+  14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission.  For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this.  Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+                           NO WARRANTY
+
+  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+                    END OF TERMS AND CONDITIONS
+\f
+           How to Apply These Terms to Your New Libraries
+
+  If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change.  You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+  To apply these terms, attach the following notices to the library.  It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the library's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This library is free software; you can redistribute it and/or
+    modify it under the terms of the GNU Lesser General Public
+    License as published by the Free Software Foundation; either
+    version 2.1 of the License, or (at your option) any later version.
+
+    This library is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+    Lesser General Public License for more details.
+
+    You should have received a copy of the GNU Lesser General Public
+    License along with this library; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the
+  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+  <signature of Ty Coon>, 1 April 1990
+  Ty Coon, President of Vice
+
+That's all there is to it!
+
+
diff --git a/contrib/gcc-3.4/FAQ b/contrib/gcc-3.4/FAQ
new file mode 100644 (file)
index 0000000..571b83e
--- /dev/null
@@ -0,0 +1,588 @@
+
+                        GCC Frequently Asked Questions
+
+   The   latest   version   of  this  document  is  always  available  at
+   [1]http://gcc.gnu.org/faq.html.
+
+   This  FAQ  tries  to  answer  specific  questions  concerning GCC. For
+   general  information  regarding C, C++, resp. Fortran please check the
+   [2]comp.lang.c   FAQ,   [3]comp.std.c++   FAQ,   and   the  [4]Fortran
+   Information page.
+
+   Other GCC-related FAQs: [5]libstdc++-v3, and [6]GCJ.
+     _________________________________________________________________
+
+                                   Questions
+
+    1. [7]General information
+         1. [8]What is the relationship between GCC and EGCS?
+         2. [9]What is an open development model?
+         3. [10]How do I get a bug fixed or a feature added?
+         4. [11]Does GCC work on my platform?
+    2. [12]Installation
+         1. [13]How to install multiple versions of GCC
+         2. [14]Dynamic linker is unable to find GCC libraries
+         3. [15]libstdc++/libio tests fail badly with --enable-shared
+         4. [16]GCC can not find GNU as/GNU ld
+         5. [17]cpp: Usage:... Error
+         6. [18]Optimizing the compiler itself
+         7. [19]Why does libiconv get linked into jc1 on Solaris?
+    3. [20]Testsuite problems
+         1. [21]How do I pass flags like -fnew-abi to the testsuite?
+         2. [22]How can I run the test suite with multiple options?
+    4. [23]Older versions of GCC
+         1. [24]Is there a stringstream / sstream for GCC 2.95.2?
+    5. [25]Miscellaneous
+         1. [26]Friend Templates
+         2. [27]dynamic_cast,   throw,  typeid  don't  work  with  shared
+            libraries
+         3. [28]Why do I need autoconf, bison, xgettext, automake, etc?
+         4. [29]Why can't I build a shared library?
+         5. [30]When  building  C++,  the  linker  says  my constructors,
+            destructors  or  virtual  tables are undefined, but I defined
+            them
+         6. [31]Will GCC someday include an incremental linker?
+     _________________________________________________________________
+
+                              General information
+
+What is the relationship between GCC and EGCS?
+
+   In  1990/1991  gcc version 1 had reached a point of stability. For the
+   targets  it could support, it worked well. It had limitations inherent
+   in  its  design  that would be difficult to resolve, so a major effort
+   was  made  to  resolve  those  limitations  and  gcc version 2 was the
+   result.
+
+   When  we  had  gcc2  in  a  useful  state, development efforts on gcc1
+   stopped  and we all concentrated on making gcc2 better than gcc1 could
+   ever  be.  This is the kind of step forward we wanted to make with the
+   EGCS project when it was formed in 1997.
+
+   In   April   1999  the  Free  Software  Foundation  officially  halted
+   development on the gcc2 compiler and appointed the EGCS project as the
+   official  GCC  maintainers.  The net result was a single project which
+   carries  forward  GCC  development  under  the ultimate control of the
+   [32]GCC Steering Committee.
+     _________________________________________________________________
+
+What is an open development model?
+
+   We  are  using  a bazaar style [33][1] approach to GCC development: we
+   make  snapshots publicly available to anyone who wants to try them; we
+   welcome  anyone  to  join  the  development  mailing  list. All of the
+   discussions on the development mailing list are available via the web.
+   We're  going  to  be making releases with a much higher frequency than
+   they have been made in the past.
+
+   In  addition  to  weekly  snapshots of the GCC development sources, we
+   have  the sources readable from a CVS server by anyone. Furthermore we
+   are  using  remote CVS to allow remote maintainers write access to the
+   sources.
+
+   There  have  been  many  potential GCC developers who were not able to
+   participate  in  GCC  development in the past. We want these people to
+   help  in  any  way  they  can;  we  ultimately want GCC to be the best
+   compiler in the world.
+
+   A  compiler  is  a  complicated piece of software, there will still be
+   strong  central  maintainers  who will reject patches, who will demand
+   documentation  of  implementations,  and  who  will  keep the level of
+   quality  as high as it is today. Code that could use wider testing may
+   be integrated--code that is simply ill-conceived won't be.
+
+   GCC  is  not  the first piece of software to use this open development
+   process;  FreeBSD, the Emacs lisp repository, and the Linux kernel are
+   a few examples of the bazaar style of development.
+
+   With  GCC, we are adding new features and optimizations at a rate that
+   has  not  been  done  since  the  creation  of  gcc2;  these additions
+   inevitably  have  a temporarily destabilizing effect. With the help of
+   developers  working  together  with this bazaar style development, the
+   resulting  stability  and quality levels will be better than we've had
+   before.
+
+     [1]  We've  been discussing different development models a lot over
+     the past few months. The paper which started all of this introduced
+     two   terms:   A   cathedral  development  model  versus  a  bazaar
+     development  model.  The paper is written by Eric S. Raymond, it is
+     called  ``The  Cathedral  and  the  Bazaar''. The paper is a useful
+     starting point for discussions.
+     _________________________________________________________________
+
+How do I get a bug fixed or a feature added?
+
+   There  are  lots of ways to get something fixed. The list below may be
+   incomplete,  but  it covers many of the common cases. These are listed
+   roughly  in  order  of decreasing difficulty for the average GCC user,
+   meaning  someone who is not skilled in the internals of GCC, and where
+   difficulty  is  measured in terms of the time required to fix the bug.
+   No  alternative  is  better  than any other; each has its benefits and
+   disadvantages.
+     * Fix  it yourself. This alternative will probably bring results, if
+       you  work  hard enough, but will probably take a lot of time, and,
+       depending  on  the quality of your work and the perceived benefits
+       of  your  changes,  your  code may or may not ever make it into an
+       official release of GCC.
+     * [34]Report  the  problem  to  the GCC bug tracking system and hope
+       that  someone will be kind enough to fix it for you. While this is
+       certainly  possible, and often happens, there is no guarantee that
+       it  will. You should not expect the same response from this method
+       that  you  would  see from a commercial support organization since
+       the  people  who read GCC bug reports, if they choose to help you,
+       will be volunteering their time.
+     * Hire  someone  to  fix it for you. There are various companies and
+       individuals  providing  support  for  GCC.  This alternative costs
+       money, but is relatively likely to get results.
+     _________________________________________________________________
+
+Does GCC work on my platform?
+
+   The   host/target   specific   installation   notes  for  GCC  include
+   information  about  known  problems  with  installing  or using GCC on
+   particular  platforms. These are included in the sources for a release
+   in   INSTALL/specific.html,  and  the  [35]latest  version  is  always
+   available  at  the  GCC web site. Reports of [36]successful builds for
+   several versions of GCC are also available at the web site.
+     _________________________________________________________________
+
+                                 Installation
+
+How to install multiple versions of GCC
+
+   It  may  be  desirable to install multiple versions of the compiler on
+   the  same  system. This can be done by using different prefix paths at
+   configure time and a few symlinks.
+
+   Basically,   configure  the  two  compilers  with  different  --prefix
+   options,  then  build and install each compiler. Assume you want "gcc"
+   to be the latest compiler and available in /usr/local/bin; also assume
+   that  you want "gcc2" to be the older gcc2 compiler and also available
+   in /usr/local/bin.
+
+   The  easiest  way  to  do  this  is  to  configure  the  new  GCC with
+   --prefix=/usr/local/gcc      and      the      older     gcc2     with
+   --prefix=/usr/local/gcc2.  Build and install both compilers. Then make
+   a  symlink  from /usr/local/bin/gcc to /usr/local/gcc/bin/gcc and from
+   /usr/local/bin/gcc2  to  /usr/local/gcc2/bin/gcc. Create similar links
+   for the "g++", "c++" and "g77" compiler drivers.
+
+   An   alternative   to   using   symlinks   is   to  configure  with  a
+   --program-transform-name  option.  This option specifies a sed command
+   to  process  installed  program  names  with.  Using  it  you can, for
+   instance, have all the new GCC programs installed as "new-gcc" and the
+   like.  You  will  still have to specify different --prefix options for
+   new  GCC  and old GCC, because it is only the executable program names
+   that are transformed. The difference is that you (as administrator) do
+   not  have  to set up symlinks, but must specify additional directories
+   in your (as a user) PATH. A complication with --program-transform-name
+   is  that the sed command invariably contains characters significant to
+   the  shell,  and  these  have  to be escaped correctly, also it is not
+   possible  to  use  "^"  or  "$"  in the command. Here is the option to
+   prefix "new-" to the new GCC installed programs:
+
+     --program-transform-name='s,\\\\(.*\\\\),new-\\\\1,'
+
+   With the above --prefix option, that will install the new GCC programs
+   into  /usr/local/gcc/bin  with  names  prefixed by "new-". You can use
+   --program-transform-name  if  you  have  multiple versions of GCC, and
+   wish to be sure about which version you are invoking.
+
+   If  you use --prefix, GCC may have difficulty locating a GNU assembler
+   or  linker on your system, [37]GCC can not find GNU as/GNU ld explains
+   how to deal with this.
+
+   Another  option  that may be easier is to use the --program-prefix= or
+   --program-suffix=  options  to  configure. So if you're installing GCC
+   2.95.2  and  don't  want  to  disturb  the  current  version of GCC in
+   /usr/local/bin/, you could do
+
+     configure --program-suffix=-2.95.2 <other configure options>
+
+   This should result in GCC being installed as /usr/local/bin/gcc-2.95.2
+   instead of /usr/local/bin/gcc.
+     _________________________________________________________________
+
+Dynamic linker is unable to find GCC libraries
+
+   This problem manifests itself by programs not finding shared libraries
+   they  depend on when the programs are started. Note this problem often
+   manifests  itself  with  failures  in  the libio/libstdc++ tests after
+   configuring with --enable-shared and building GCC.
+
+   GCC  does  not  specify  a runpath so that the dynamic linker can find
+   dynamic libraries at runtime.
+
+   The  short  explanation  is that if you always pass a -R option to the
+   linker,  then  your programs become dependent on directories which may
+   be NFS mounted, and programs may hang unnecessarily when an NFS server
+   goes down.
+
+   The  problem  is  not  programs that do require the directories; those
+   programs  are  going  to  hang  no  matter what you do. The problem is
+   programs that do not require the directories.
+
+   SunOS  effectively always passed a -R option for every -L option; this
+   was  a  bad  idea,  and  so  it was removed for Solaris. We should not
+   recreate it.
+
+   However,  if  you  feel  you  really  need such an option to be passed
+   automatically  to  the  linker,  you may add it to the GCC specs file.
+   This  file  can  be found in the same directory that contains cc1 (run
+   gcc -print-prog-name=cc1 to find it). You may add linker flags such as
+   -R  or  -rpath, depending on platform and linker, to the *link or *lib
+   specs.
+
+   Another  alternative is to install a wrapper script around gcc, g++ or
+   ld  that  adds  the  appropriate directory to the environment variable
+   LD_RUN_PATH or equivalent (again, it's platform-dependent).
+
+   Yet another option, that works on a few platforms, is to hard-code the
+   full  pathname  of  the  library  into  its  soname.  This can only be
+   accomplished   by   modifying   the   appropriate   .ml   file  within
+   libstdc++/config (and also libg++/config, if you are building libg++),
+   so  that $(libdir)/ appears just before the library name in -soname or
+   -h options.
+     _________________________________________________________________
+
+GCC can not find GNU as/GNU ld
+
+   GCC  searches the PATH for an assembler and a loader, but it only does
+   so after searching a directory list hard-coded in the GCC executables.
+   Since,  on most platforms, the hard-coded list includes directories in
+   which  the  system  assembler and loader can be found, you may have to
+   take  one  of  the  following actions to arrange that GCC uses the GNU
+   versions of those programs.
+
+   To ensure that GCC finds the GNU assembler (the GNU loader), which are
+   required  by  [38]some configurations, you should configure these with
+   the same --prefix option as you used for GCC. Then build & install GNU
+   as (GNU ld) and proceed with building GCC.
+
+   Another  alternative is to create links to GNU as and ld in any of the
+   directories  printed  by  the  command  `gcc -print-search-dirs | grep
+   '^programs:''.  The  link  to  `ld'  should be named `real-ld' if `ld'
+   already exists. If such links do not exist while you're compiling GCC,
+   you  may  have to create them in the build directories too, within the
+   gcc directory and in all the gcc/stage* subdirectories.
+
+   GCC  2.95 allows you to specify the full pathname of the assembler and
+   the linker to use. The configure flags are `--with-as=/path/to/as' and
+   `--with-ld=/path/to/ld'.  GCC  will  try to use these pathnames before
+   looking  for  `as'  or `(real-)ld' in the standard search dirs. If, at
+   configure-time,  the specified programs are found to be GNU utilities,
+   `--with-gnu-as' and `--with-gnu-ld' need not be used; these flags will
+   be  auto-detected.  One drawback of this option is that it won't allow
+   you  to  override  the  search  path  for  assembler  and  linker with
+   command-line options -B/path/ if the specified filenames exist.
+     _________________________________________________________________
+
+cpp: Usage:... Error
+
+   If  you  get  an  error like this when building GCC (particularly when
+   building   __mulsi3),  then  you  likely  have  a  problem  with  your
+   environment variables.
+  cpp: Usage: /usr/lib/gcc-lib/i586-unknown-linux-gnulibc1/2.7.2.3/cpp
+  [switches] input output
+
+   First   look   for   an   explicit   '.'  in  either  LIBRARY_PATH  or
+   GCC_EXEC_PREFIX  from your environment. If you do not find an explicit
+   '.',  look  for an empty pathname in those variables. Note that ':' at
+   either the start or end of these variables is an implicit '.' and will
+   cause problems.
+
+   Also note '::' in these paths will also cause similar problems.
+     _________________________________________________________________
+
+Optimizing the compiler itself
+
+   If  you  want to test a particular optimization option, it's useful to
+   try  bootstrapping  the  compiler  with  that  option  turned  on. For
+   example, to test the -fssa option, you could bootstrap like this:
+make BOOT_CFLAGS="-O2 -fssa" bootstrap
+     _________________________________________________________________
+
+Why does libiconv get linked into jc1 on Solaris?
+
+   The  Java  front end requires iconv. If the compiler used to bootstrap
+   GCC  finds  libiconv  (because  the  GNU  version of libiconv has been
+   installed in the same prefix as the bootstrap compiler), but the newly
+   built GCC does not find the library (because it will be installed with
+   a  different  prefix), then a link-time error will occur when building
+   jc1.  This  problem  does  not show up so often on platforms that have
+   libiconv  in  a  default  location  (like  /usr/lib) because then both
+   compilers  can  find  a  library  named  libiconv, even though it is a
+   different library.
+
+   Using  --disable-nls  at  configure-time does not prevent this problem
+   because   jc1   uses  iconv  even  in  that  case.  Solutions  include
+   temporarily  removing  the  GNU  libiconv,  copying  it  to  a default
+   location   such   as   /usr/lib/,   and  using  --enable-languages  at
+   configure-time to disable Java.
+     _________________________________________________________________
+
+                              Testsuite problems
+
+How do I pass flags like -fnew-abi to the testsuite?
+
+   If  you  invoke  runtest directly, you can use the --tool_opts option,
+   e.g:
+  runtest --tool_opts "-fnew-abi -fno-honor-std" <other options>
+
+   Or,  if you use make check you can use the make variable RUNTESTFLAGS,
+   e.g:
+  make RUNTESTFLAGS="--tool_opts '-fnew-abi -fno-honor-std'" check-g++
+     _________________________________________________________________
+
+How can I run the test suite with multiple options?
+
+   If you invoke runtest directly, you can use the --target_board option,
+   e.g:
+  runtest --target_board "unix{-fPIC,-fpic,}" <other options>
+
+   Or,  if you use make check you can use the make variable RUNTESTFLAGS,
+   e.g:
+  make RUNTESTFLAGS="--target_board 'unix{-fPIC,-fpic,}'" check-gcc
+
+   Either  of  these  examples  will run the tests three times. Once with
+   -fPIC, once with -fpic, and once with no additional flags.
+
+   This technique is particularly useful on multilibbed targets.
+     _________________________________________________________________
+
+                        Older versions of GCC and EGCS
+
+Is there a stringstream / sstream for GCC 2.95.2?
+
+   Yes, it's at:
+   [39]http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream.
+     _________________________________________________________________
+
+                                 Miscellaneous
+
+Friend Templates
+
+   In order to make a specialization of a template function a friend of a
+   (possibly  template)  class, you must explicitly state that the friend
+   function  is  a template, by appending angle brackets to its name, and
+   this  template  function  must  have  been declared already. Here's an
+   example:
+template <typename T> class foo {
+  friend void bar(foo<T>);
+}
+
+   The  above  declaration declares a non-template function named bar, so
+   it  must  be  explicitly  defined  for  each  specialization of foo. A
+   template  definition of bar won't do, because it is unrelated with the
+   non-template declaration above. So you'd have to end up writing:
+void bar(foo<int>) { /* ... */ }
+void bar(foo<void>) { /* ... */ }
+
+   If  you  meant  bar  to  be  a  template  function,  you  should  have
+   forward-declared it as follows. Note that, since the template function
+   declaration  refers  to the template class, the template class must be
+   forward-declared too:
+template <typename T>
+class foo;
+
+template <typename T>
+void bar(foo<T>);
+
+template <typename T>
+class foo {
+  friend void bar<>(foo<T>);
+};
+
+template <typename T>
+void bar(foo<T>) { /* ... */ }
+
+   In  this case, the template argument list could be left empty, because
+   it  can  be  implicitly  deduced  from the function arguments, but the
+   angle  brackets  must  be  present,  otherwise the declaration will be
+   taken  as a non-template function. Furthermore, in some cases, you may
+   have   to   explicitly  specify  the  template  arguments,  to  remove
+   ambiguity.
+
+   An error in the last public comment draft of the ANSI/ISO C++ Standard
+   and  the  fact  that previous releases of GCC would accept such friend
+   declarations  as  template declarations has led people to believe that
+   the forward declaration was not necessary, but, according to the final
+   version of the Standard, it is.
+     _________________________________________________________________
+
+dynamic_cast, throw, typeid don't work with shared libraries
+
+   The new C++ ABI in the GCC 3.0 series uses address comparisons, rather
+   than string compares, to determine type equality. This leads to better
+   performance.  Like  other objects that have to be present in the final
+   executable,  these  std::typeinfo_t  objects have what is called vague
+   linkage  because  they  are  not  tightly  bound to any one particular
+   translation  unit  (object file). The compiler has to emit them in any
+   translation  unit  that  requires their presence, and then rely on the
+   linking  and  loading  process  to  make sure that only one of them is
+   active  in  the  final  executable.  With  static linking all of these
+   symbols  are  resolved at link time, but with dynamic linking, further
+   resolution occurs at load time. You have to ensure that objects within
+   a  shared  library  are resolved against objects in the executable and
+   other shared libraries.
+     * For  a  program  which  is  linked  against  a  shared library, no
+       additional precautions need taking.
+     * You  cannot  create a shared library with the "-Bsymbolic" option,
+       as that prevents the resolution described above.
+     * If  you  use dlopen to explicitly load code from a shared library,
+       you  must do several things. First, export global symbols from the
+       executable  by  linking  it  with  the "-E" flag (you will have to
+       specify  this  as  "-Wl,-E"  if you are invoking the linker in the
+       usual  manner  from  the compiler driver, g++). You must also make
+       the   external   symbols  in  the  loaded  library  available  for
+       subsequent  libraries by providing the RTLD_GLOBAL flag to dlopen.
+       The symbol resolution can be immediate or lazy.
+
+   Template  instantiations  are  another,  user visible, case of objects
+   with vague linkage, which needs similar resolution. If you do not take
+   the  above precautions, you may discover that a template instantiation
+   with  the same argument list, but instantiated in multiple translation
+   units,  has several addresses, depending in which translation unit the
+   address  is  taken.  (This  is  not  an exhaustive list of the kind of
+   objects  which  have  vague  linkage  and  are expected to be resolved
+   during linking & loading.)
+
+   If  you  are  worried  about  different  objects  with  the  same name
+   colliding  during  the linking or loading process, then you should use
+   namespaces  to  disambiguate them. Giving distinct objects with global
+   linkage  the same name is a violation of the One Definition Rule (ODR)
+   [basic.def.odr].
+
+   For more details about the way that GCC implements these and other C++
+   features,   please   read   the   [40]ABI   specification.   Note  the
+   std::typeinfo_t  objects which must be resolved all begin with "_ZTS".
+   Refer   to  ld's  documentation  for  a  description  of  the  "-E"  &
+   "-Bsymbolic" flags.
+     _________________________________________________________________
+
+Why do I need autoconf, bison, xgettext, automake, etc?
+
+   If  you're  using  diffs up dated from one snapshot to the next, or if
+   you're  using  the  CVS  repository,  you  may need several additional
+   programs to build GCC.
+
+   These  include, but are not necessarily limited to autoconf, automake,
+   bison, and xgettext.
+
+   This  is  necessary  because  neither  diff  nor  cvs  keep timestamps
+   correct.  This causes problems for generated files as "make" may think
+   those generated files are out of date and try to regenerate them.
+
+   An  easy  way  to  work  around  this problem is to use the gcc_update
+   script  in  the  contrib  subdirectory  of  GCC,  which  handles  this
+   transparently  without requiring installation of any additional tools.
+   (Note: Up to and including GCC 2.95 this script was called egcs_update
+   .)
+
+   When  building  from diffs or CVS or if you modified some sources, you
+   may also need to obtain development versions of some GNU tools, as the
+   production  versions  do not necessarily handle all features needed to
+   rebuild GCC.
+
+   In    general,    the   current   versions   of   these   tools   from
+   [41]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not
+   supported, and you will need to use Autoconf 2.13; work is in progress
+   to fix this problem. Also look at
+   [42]ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions
+   of packages.
+     _________________________________________________________________
+
+Why can't I build a shared library?
+
+   When  building  a shared library you may get an error message from the
+   linker like `assert pure-text failed:' or `DP relative code in file'.
+
+   This  kind  of error occurs when you've failed to provide proper flags
+   to gcc when linking the shared library.
+
+   You can get this error even if all the .o files for the shared library
+   were  compiled  with  the  proper  PIC  option. When building a shared
+   library,  gcc  will  compile  additional  code  to  be included in the
+   library.  That  additional  code must also be compiled with the proper
+   PIC option.
+
+   Adding  the  proper PIC option (-fpic or -fPIC) to the link line which
+   creates  the  shared  library  will  fix  this problem on targets that
+   support PIC in this manner. For example:
+        gcc -c -fPIC myfile.c
+        gcc -shared -o libmyfile.so -fPIC myfile.o
+     _________________________________________________________________
+
+When building C++, the linker says my constructors, destructors or virtual
+tables are undefined, but I defined them
+
+   The  ISO  C++  Standard  specifies that all virtual methods of a class
+   that  are  not  pure-virtual must be defined, but does not require any
+   diagnostic  for  violations  of  this rule [class.virtual]/8. Based on
+   this   assumption,   GCC   will   only  emit  the  implicitly  defined
+   constructors,  the assignment operator, the destructor and the virtual
+   table  of  a class in the translation unit that defines its first such
+   non-inline method.
+
+   Therefore,  if  you  fail to define this particular method, the linker
+   may  complain  about  the lack of definitions for apparently unrelated
+   symbols.  Unfortunately,  in  order  to improve this error message, it
+   might  be  necessary  to  change  the linker, and this can't always be
+   done.
+
+   The  solution  is to ensure that all virtual methods that are not pure
+   are  defined.  Note  that  a  destructor must be defined even if it is
+   declared pure-virtual [class.dtor]/7.
+     _________________________________________________________________
+
+Will GCC someday include an incremental linker?
+
+   Incremental  linking is part of the linker, not the compiler. As such,
+   GCC doesn't have anything to do with incremental linking. Depending on
+   what  platform  you  use,  it  may  be possible to tell GCC to use the
+   platform's native linker (e.g., Solaris' ild(1)).
+
+References
+
+   1. http://gcc.gnu.org/faq.html
+   2. http://www.eskimo.com/~scs/C-faq/top.html
+   3. http://www.jamesd.demon.co.uk/csc/faq.html
+   4. http://www.fortran.com/fortran/info.html
+   5. http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html
+   6. http://gcc.gnu.org/java/faq.html
+   7. http://gcc.gnu.org/faq.html#general
+   8. http://gcc.gnu.org/faq.html#gcc
+   9. http://gcc.gnu.org/faq.html#open-development
+  10. http://gcc.gnu.org/faq.html#support
+  11. http://gcc.gnu.org/faq.html#platforms
+  12. http://gcc.gnu.org/faq.html#installation
+  13. http://gcc.gnu.org/faq.html#multiple
+  14. http://gcc.gnu.org/faq.html#rpath
+  15. http://gcc.gnu.org/faq.html#rpath
+  16. http://gcc.gnu.org/faq.html#gas
+  17. http://gcc.gnu.org/faq.html#environ
+  18. http://gcc.gnu.org/faq.html#optimizing
+  19. http://gcc.gnu.org/faq.html#iconv
+  20. http://gcc.gnu.org/faq.html#testsuite
+  21. http://gcc.gnu.org/faq.html#testoptions
+  22. http://gcc.gnu.org/faq.html#multipletests
+  23. http://gcc.gnu.org/faq.html#old
+  24. http://gcc.gnu.org/faq.html#2.95sstream
+  25. http://gcc.gnu.org/faq.html#misc
+  26. http://gcc.gnu.org/faq.html#friend
+  27. http://gcc.gnu.org/faq.html#dso
+  28. http://gcc.gnu.org/faq.html#generated_files
+  29. http://gcc.gnu.org/faq.html#picflag-needed
+  30. http://gcc.gnu.org/faq.html#vtables
+  31. http://gcc.gnu.org/faq.html#incremental
+  32. http://gcc.gnu.org/steering.html
+  33. http://gcc.gnu.org/faq.html#cathedral-vs-bazaar
+  34. http://gcc.gnu.org/bugs.html
+  35. http://gcc.gnu.org/install/specific.html
+  36. http://gcc.gnu.org/buildstat.html
+  37. http://gcc.gnu.org/faq.html#gas
+  38. http://gcc.gnu.org/install/specific.html
+  39. http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream
+  40. http://www.codesourcery.com/cxx-abi/
+  41. ftp://ftp.gnu.org/gnu/
+  42. ftp://gcc.gnu.org/pub/gcc/infrastructure/
diff --git a/contrib/gcc-3.4/LAST_UPDATED b/contrib/gcc-3.4/LAST_UPDATED
new file mode 100644 (file)
index 0000000..51be09d
--- /dev/null
@@ -0,0 +1 @@
+Obtained from CVS: -rgcc-ss-3_4-20040618 
diff --git a/contrib/gcc-3.4/MAINTAINERS b/contrib/gcc-3.4/MAINTAINERS
new file mode 100644 (file)
index 0000000..b7ded19
--- /dev/null
@@ -0,0 +1,291 @@
+Note
+====
+
+This file contains information about people who are permitted to make
+changes to various parts of the compiler and associated libraries.
+
+Please do not contact the people in this file directly to report
+problems in GCC.
+
+For general information about GCC, please visit:
+
+  http://gcc.gnu.org
+
+To report problems in GCC, please visit:
+
+  http://gcc.gnu.org/bugs.html
+
+Maintainers
+===========
+
+                       Blanket Write Privs.
+
+Richard Earnshaw                               rearnsha@arm.com
+Richard Henderson                               rth@redhat.com
+Geoffrey Keating                               geoffk@geoffk.org
+Richard Kenner                                 kenner@nyu.edu
+Jeff Law                                       law@redhat.com
+Michael Meissner                               gnu@the-meissners.org
+Jason Merrill                                  jason@redhat.com
+David S. Miller                                        davem@redhat.com
+Mark Mitchell                                  mark@codesourcery.com
+Bernd Schmidt                                  bernds@redhat.com
+Zack Weinberg                                  zack@codesourcery.com
+Jim Wilson                                     wilson@specifixinc.com
+
+
+                       CPU Port Maintainers    (CPU alphabetical order)
+
+alpha port             Richard Henderson       rth@redhat.com
+arm port               Nick Clifton            nickc@redhat.com
+arm port               Richard Earnshaw        rearnsha@arm.com
+avr port               Denis Chertykov         denisc@overta.ru
+avr port               Marek Michalkiewicz     marekm@amelek.gda.pl
+c4x port               Michael Hayes           m.hayes@elec.canterbury.ac.nz
+cris port              Hans-Peter Nilsson      hp@axis.com
+fr30 port              Nick Clifton            nickc@redhat.com
+h8 port                        Jeff Law                law@redhat.com
+h8 port                        Kazu Hirata             kazu@cs.umass.edu
+hppa port              Jeff Law                law@redhat.com
+hppa port              Dave Anglin             dave.anglin@nrc.ca
+i386 port              Richard Henderson       rth@redhat.com
+i860 port              Jason Eckhardt          jle@rice.edu
+i960 port              Jim Wilson              wilson@specifixinc.com
+ia64 port              Jim Wilson              wilson@specifixinc.com
+ip2k port              Denis Chertykov         denisc@overta.ru
+iq2000 port            Stan Cox                scox@redhat.com
+m32r port              Nick Clifton            nickc@redhat.com
+m68hc11 port           Stephane Carrez         stcarrez@nerim.fr
+m68k port (?)          Jeff Law                law@redhat.com
+m68k-motorola-sysv port        Philippe De Muyter      phdm@macqel.be
+mcore port             Nick Clifton            nickc@redhat.com
+mips port               Eric Christopher        echristo@redhat.com
+mips port              Richard Sandiford       rsandifo@redhat.com
+mmix port              Hans-Peter Nilsson      hp@bitrange.com
+mn10300 port           Jeff Law                law@redhat.com
+mn10300 port           Alexandre Oliva         aoliva@redhat.com
+ns32k port             Ian Dall                ian@beware.dropbear.id.au
+pdp11 port             Paul Koning             ni1d@arrl.net
+rs6000 port            Geoff Keating           geoffk@geoffk.org
+rs6000 port            David Edelsohn          dje@watson.ibm.com
+rs6000 vector extns    Aldy Hernandez          aldyh@redhat.com
+s390 port              Hartmut Penner          hpenner@de.ibm.com
+s390 port              Ulrich Weigand          uweigand@de.ibm.com
+sh port                        Joern Rennecke          joern.rennecke@superh.com
+sh port                        Alexandre Oliva         aoliva@redhat.com
+sparc port             Richard Henderson       rth@redhat.com
+sparc port             David S. Miller         davem@redhat.com
+sparc port             Jakub Jelinek           jakub@redhat.com
+sparc port             Eric Botcazou           ebotcazou@libertysurf.fr
+v850 port              Nick Clifton            nickc@redhat.com
+vax port               Dave Anglin             dave.anglin@nrc.ca
+vax port               Matt Thomas             matt@3am-software.com
+x86-64 port            Jan Hubicka             jh@suse.cz
+xstormy16 port         Geoffrey Keating        geoffk@geoffk.org
+xtensa port            Bob Wilson              bob.wilson@acm.org
+
+                       OS Port Maintainers     (OS alphabetical order)
+
+darwin port            Stan Shebs              shebs@apple.com
+freebsd                        Loren J. Rittle         ljrittle@acm.org
+netbsd                 Jason Thorpe            thorpej@wasabisystems.com
+sco5, unixware, sco udk        Kean Johnston           jkj@sco.com
+sh-linux-gnu           Kaz Kojima              kkojima@gcc.gnu.org
+
+                       Various Maintainers
+
+C front end/ISO C99    Joseph Myers            jsm@polyomino.org.uk
+C front end/ISO C99    Richard Henderson       rth@redhat.com
+Ada front end          Geert Bosch             bosch@gnat.com
+Ada front end          Robert Dewar            dewar@gnat.com
+Ada front end          Arnaud Charlet          charlet@act-europe.fr
+fortran                        Richard Henderson       rth@redhat.com
+fortran                        Toon Moene              toon@moene.indiv.nluug.nl
+fortran 95             Paul Brook              paul@nowt.org
+fortran 95             Steven Bosscher         stevenb@suse.de
+fortran 95             Toon Moene              toon@moene.indiv.nluug.nl
+c++                    Jason Merrill           jason@redhat.com
+c++                     Mark Mitchell          mark@codesourcery.com
+cpplib                 Dave Brolley            brolley@redhat.com
+cpplib                 Per Bothner             per@bothner.com
+cpplib                 Zack Weinberg           zack@codesourcery.com
+cpplib                 Neil Booth              neil@daikokuya.co.uk
+java                   Per Bothner             per@bothner.com
+java                   Andrew Haley            aph@redhat.com
+libgcj                 Tom Tromey              tromey@redhat.com
+libgcj                 Bryce McKinlay          bryce@gcc.gnu.org
+mercury                        Fergus Henderson        fjh@cs.mu.oz.au
+objective-c            Stan Shebs              shebs@apple.com
+objective-c            Ovidiu Predescu         ovidiu@cup.hp.com
+objective-c            Ziemowit Laski          zlaski@apple.com
+libobjc                        Nicola Pero             n.pero@mi.flashnet.it
+libobjc                        Andrew Pinski           pinskia@physics.uc.edu
+alias analysis         John Carr               jfc@mit.edu
+loop unrolling         Jim Wilson              wilson@specifixinc.com
+loop discovery         Michael Hayes           m.hayes@elec.canterbury.ac.nz
+scheduler (+ haifa)    Jim Wilson              wilson@specifixinc.com
+scheduler (+ haifa)    Michael Meissner        gnu@the-meissners.org
+scheduler (+ haifa)    Jeff Law                law@redhat.com
+reorg                  Jeff Law                law@redhat.com
+caller-save.c          Jeff Law                law@redhat.com
+callgraph              Jan Hubicka             jh@suse.cz
+debugging code         Jim Wilson              wilson@specifixinc.com
+dwarf debugging code   Jason Merrill           jason@redhat.com
+c++ runtime libs       Paolo Carlini           pcarlini@suse.de
+c++ runtime libs        Gabriel Dos Reis        gdr@integrable-solutions.net
+c++ runtime libs       Ulrich Drepper          drepper@redhat.com
+c++ runtime libs       Phil Edwards            pme@gcc.gnu.org
+c++ runtime libs       Benjamin Kosnik         bkoz@redhat.com
+c++ runtime libs       Loren J. Rittle         ljrittle@acm.org
+*synthetic multiply    Torbjorn Granlund       tege@swox.com
+*c-torture             Torbjorn Granlund       tege@swox.com
+fixincludes            Bruce Korb              bkorb@gnu.org
+gcse.c                         Jeff Law                law@redhat.com
+global opt framework   Jeff Law                law@redhat.com
+jump.c                 David S. Miller         davem@redhat.com
+web pages              Gerald Pfeifer          gerald@pfeifer.com
+web pages              Janis Johnson           janis187@us.ibm.com
+config.sub/config.guess        Ben Elliston            config-patches@gnu.org
+basic block reordering Jason Eckhardt          jle@rice.edu
+i18n                   Philipp Thomas          pthomas@suse.de
+diagnostic messages    Gabriel Dos Reis        gdr@integrable-solutions.net
+windows, cygwin, mingw Christopher Faylor      cgf@redhat.com
+DJGPP                  DJ Delorie              dj@delorie.com
+libiberty              DJ Delorie              dj@redhat.com
+libiberty              Ian Lance Taylor        ian@wasabisystems.com
+build machinery (*.in) DJ Delorie              dj@redhat.com
+build machinery (*.in) Nathanael Nerode        neroden@gcc.gnu.org
+build machinery (*.in) Alexandre Oliva         aoliva@redhat.com
+docs co-maintainer     Gerald Pfeifer          gerald@pfeifer.com
+docs co-maintainer     Joseph Myers            jsm@polyomino.org.uk
+Pico-Java port         Steve Chamberlain       sac@transmeta.com
+RTEMS Ports            Joel Sherrill           joel@oarcorp.com
+VxWorks        ports           Zack Weinberg           zack@codesourcery.com
+VxWorks        ports           Nathan Sidwell          nathan@codesourcery.com
+predict.def            Jan Hubicka             jh@suse.cz
+contrib/regression     Geoff Keating           geoffk@geoffk.org
+treelang                Tim Josling             tej@melbpc.org.au
+new regalloc (ra*)     Michael Matz            matz@suse.de
+gcov                   Jan Hubicka             jh@suse.cz
+gcov                   Nathan Sidwell          nathan@codesourcery.com
+option handling                Neil Booth              neil@daikokuya.co.uk
+libffi testsuite       Andreas Tobler          andreast@gcc.gnu.org
+middle-end             Roger Sayle             roger@eyesopen.com
+
+Note individuals who maintain parts of the compiler need approval to check
+in changes outside of the parts of the compiler they maintain.
+
+
+                       Write After Approval    (last name alphabetical order)
+
+Matt Austern                                    austern@apple.com
+Giovanni Bajo                                  giovannibajo@gcc.gnu.org
+Scott Bambrough                                        scottb@netwinder.org
+Wolfgang Bangerth                              bangerth@dealii.org
+Daniel Berlin                                  dan@dberlin.org
+David Billinghurst                             David.Billinghurst@riotinto.com
+Laurynas Biveinis                              laurynas.biveinis@mif.vu.lt
+Eric Blake                                     ericb@gcc.gnu.org
+Jim Blandy                                     jimb@redhat.com
+Phil Blundell                                  pb@futuretv.com
+Hans Boehm                                     hboehm@gcc.gnu.org
+Robert Bowdidge                                 bowdidge@apple.com
+Joel Brobecker                                 brobecker@gnat.com
+Kevin Buettner                                 kevinb@redhat.com
+Andrew Cagney                                  cagney@redhat.com
+Chandra Chavva                                 cchavva@redhat.com
+William Cohen                                  wcohen@redhat.com
+R. Kelley Cook                                 kcook@gcc.gnu.org
+Christian Cornelssen                           ccorn@cs.tu-berlin.de
+David Daney                                    ddaney@avtrex.com
+Chris Demetriou                                        cgd@broadcom.com
+Zdenek Dvorak                                  dvorakz@suse.cz
+Steve Ellcey                                   sje@cup.hp.com
+Ben Elliston                                   bje@wasabisystems.com
+Mohan Embar                                    gnustuff@thisiscool.com
+Marc Espie                                     espie@cvs.openbsd.org
+Ansgar Esztermann                              ansgar@thphy.uni-duesseldorf.de
+Doug Evans                                     dje@transmeta.com
+Kaveh Ghazi                                    ghazi@caip.rutgers.edu
+Matthew Gingell                                        gingell@gnat.com
+Anthony Green                                  green@redhat.com
+Laurent Guerby                                 guerby@acm.org
+Olivier Hainque                                        hainque@act-europe.fr
+Stuart Hastings                                        stuart@apple.com
+Matthew Hiller                                 hiller@redhat.com
+Manfred Hollstein                              mh@suse.com
+Falk Hueffner                                  falk@debian.org
+Bernardo Innocenti                             bernie@develer.com
+Daniel Jacobowitz                              dan@debian.org
+Andreas Jaeger                                 aj@suse.de
+Fariborz Jahanian                              fjahanian@apple.com
+Dale Johannesen                                dalej@apple.com
+Klaus Kaempf                                   kkaempf@progis.de
+Brendan Kehoe                                  brendan@zen.org
+Mumit Khan                                     khan@xraylith.wisc.edu
+Matthias Klose                                 doko@debian.org
+Jeff Knaggs                                    jknaggs@redhat.com
+Matt Kraai                                     kraai@alumni.cmu.edu
+Marc Lehmann                                   pcg@goof.com
+Alan Lehotsky                                  apl@alum.mit.edu
+James Lemke                                    jim@wasabisystems.com
+Kriang Lerdsuwanakij                           lerdsuwa@users.sourceforge.net
+Warren Levy                                    warrenl@cruzio.com
+Don Lindsay                                    dlindsay@redhat.com
+Ralph Loader                                   rcl@ihug.co.nz
+Dave Love                                      d.love@dl.ac.uk
+Martin v. Löwis                                        loewis@informatik.hu-berlin.de
+HJ Lu                                          hjl@lucon.org
+Andrew Macleod                                 amacleod@redhat.com
+Vladimir Makarov                               vmakarov@redhat.com
+Greg McGary                                    gkm@gnu.org
+Adam Megacz                                    adam@xwt.org
+Alan Modra                                     amodra@bigpond.net.au
+Catherine Moore                                        clm@redhat.com
+Dorit Naishlos                                  dorit@il.ibm.com
+Adam Nemet                                     anemet@lnxw.com
+Dan Nicolaescu                                 dann@ics.uci.edu
+Diego Novillo                                  dnovillo@redhat.com
+David O'Brien                                  obrien@FreeBSD.org
+Turly O'Connor                                 turly@apple.com
+Jeffrey D. Oldham                              oldham@codesourcery.com
+Rainer Orth                                    ro@TechFak.Uni-Bielefeld.DE
+Devang Patel                                   dpatel@apple.com
+Graeme Peterson                                        gp@qnx.com
+Alexandre Petit-Bianco                         apbianco@redhat.com
+Nicolas Pitre                                  nico@cam.org
+Sebastian Pop                                   s.pop@laposte.net
+Clinton Popetz                                 cpopetz@cpopetz.com
+Jerry Quinn                                    jlquinn@optonline.net
+Rolf Rasmussen                                 rolfwr@gcc.gnu.org
+Volker Reichelt                                        reichelt@igpm.rwth-aachen.de
+Tom Rix                                                trix@redhat.com
+Craig Rodrigues                                        rodrigc@gcc.gnu.org
+Gavin Romig-Koch                               gavin@redhat.com
+Ira Ruben                                      ira@apple.com
+Douglas Rupp                                   rupp@gnat.com
+Alex Samuel                                    samuel@codesourcery.com
+Andreas Schwab                                 schwab@suse.de
+Svein Seldal                                    svein.seldal@solidas.com
+Franz Sirl                                     franz.sirl-kernel@lauterbach.com
+Danny Smith                                    dannysmith@users.sourceforge.net
+Michael Sokolov                                        msokolov@ivan.Harhan.ORG
+Richard Stallman                               rms@gnu.org
+Graham Stott                                   graham.stott@btinternet.com
+Mike Stump                                     mrs@apple.com
+Jeff Sturm                                     jsturm@gcc.gnu.org
+Kresten Krab Thorup                            krab@gcc.gnu.org
+Michael Tiemann                                        tiemann@redhat.com
+Jonathan Wakely                                        redi@gcc.gnu.org
+Krister Walfridsson                            cato@df.lth.se
+John Wehle                                     john@feith.com
+Florian Weimer                                 fw@deneb.enyo.de
+Mark Wielaard                                  mark@gcc.gnu.org
+Carlo Wood                                     carlo@alinoe.com
+Josef Zlomek                                   zlomekj@suse.cz
+
+Bug database only accounts
+
+James Dennett                                  jdennett@acm.org
+Christian Ehrhardt                             ehrhardt@mathematik.uni-ulm.de
+Dara Hazeghi                                   dhazeghi@yahoo.com
diff --git a/contrib/gcc-3.4/README b/contrib/gcc-3.4/README
new file mode 100644 (file)
index 0000000..3a49513
--- /dev/null
@@ -0,0 +1,17 @@
+This directory contains the GNU Compiler Collection (GCC).
+
+The GNU Compiler Collection is free software.  See the file COPYING
+for copying permission.  The manuals, and some of the runtime
+libraries, are under different terms; see the individual source files
+for details.
+
+The directory INSTALL contains copies of the installation information
+as HTML and plain text.  The source of this information is
+gcc/doc/install.texi.  The installation information includes details
+of what is included in the GCC sources and what files GCC installs.
+
+See the file gcc/doc/gcc.texi (together with other files that it
+includes) for usage and porting information.  An online readable
+version of the manual is in the files gcc/doc/gcc.info*.
+
+See http://gcc.gnu.org/bugs.html for how to report bugs usefully.
diff --git a/contrib/gcc-3.4/README.DELETED b/contrib/gcc-3.4/README.DELETED
new file mode 100644 (file)
index 0000000..337af5c
--- /dev/null
@@ -0,0 +1,448 @@
+./.cvsignore
+./ABOUT-NLS
+./ChangeLog
+./INSTALL
+./INSTALL/README
+./MD5SUMS
+./Makefile.def
+./Makefile.in
+./Makefile.tpl
+./bugs.html
+./config
+./config-ml.in
+./config.guess
+./config.if
+./config.rpath
+./config.sub
+./configure
+./configure.in
+./contrib
+./faq.html
+./gcc.patch
+./gcc/.cvsignore
+./gcc/ABOUT-GCC-NLS
+./gcc/ChangeLog
+./gcc/ChangeLog.0
+./gcc/ChangeLog.1
+./gcc/ChangeLog.10
+./gcc/ChangeLog.2
+./gcc/ChangeLog.3
+./gcc/ChangeLog.4
+./gcc/ChangeLog.5
+./gcc/ChangeLog.6
+./gcc/ChangeLog.7
+./gcc/ChangeLog.8
+./gcc/ChangeLog.9
+./gcc/ChangeLog.lib
+./gcc/FSFChangeLog
+./gcc/FSFChangeLog.10
+./gcc/FSFChangeLog.11
+./gcc/LANGUAGES
+./gcc/Makefile.in
+./gcc/ONEWS
+./gcc/README-fixinc
+./gcc/README.Portability
+./gcc/aclocal.m4
+./gcc/config.build
+./gcc/config.gcc
+./gcc/config.host
+./gcc/config.in
+./gcc/config/alpha
+./gcc/config/arc
+./gcc/config/arm
+./gcc/config/avr
+./gcc/config/c4x
+./gcc/config/chorus.h
+./gcc/config/cris
+./gcc/config/d30v
+./gcc/config/darwin-c.c
+./gcc/config/darwin-crt2.c
+./gcc/config/darwin-protos.h
+./gcc/config/darwin.c
+./gcc/config/darwin.h
+./gcc/config/dbx.h
+./gcc/config/dbxcoff.h
+./gcc/config/divmod.c
+./gcc/config/dsp16xx
+./gcc/config/fp-bit.c
+./gcc/config/fp-bit.h
+./gcc/config/fr30
+./gcc/config/freebsd-nthr.h
+./gcc/config/freebsd-spec.h
+./gcc/config/freebsd.h
+./gcc/config/frv
+./gcc/config/gnu.h
+./gcc/config/gofast.h
+./gcc/config/h8300
+./gcc/config/i370
+./gcc/config/i386/beos-elf.h
+./gcc/config/i386/crtdll.h
+./gcc/config/i386/cygming.h
+./gcc/config/i386/cygwin.asm
+./gcc/config/i386/cygwin.h
+./gcc/config/i386/cygwin1.c
+./gcc/config/i386/cygwin2.c
+./gcc/config/i386/darwin.h
+./gcc/config/i386/djgpp.h
+./gcc/config/i386/freebsd-aout.h
+./gcc/config/i386/freebsd.h
+./gcc/config/i386/freebsd64.h
+./gcc/config/i386/gmon-sol2.c
+./gcc/config/i386/gnu.h
+./gcc/config/i386/gstabs.h
+./gcc/config/i386/gthr-win32.c
+./gcc/config/i386/i386-aout.h
+./gcc/config/i386/i386-coff.h
+./gcc/config/i386/i386-interix.h
+./gcc/config/i386/i386-interix3.h
+./gcc/config/i386/kaos-i386.h
+./gcc/config/i386/kfreebsdgnu.h
+./gcc/config/i386/libgcc-x86_64-glibc.ver
+./gcc/config/i386/linux-aout.h
+./gcc/config/i386/linux.h
+./gcc/config/i386/linux64.h
+./gcc/config/i386/lynx-ng.h
+./gcc/config/i386/lynx.h
+./gcc/config/i386/mach.h
+./gcc/config/i386/mingw32.h
+./gcc/config/i386/moss.h
+./gcc/config/i386/netbsd-elf.h
+./gcc/config/i386/netbsd.h
+./gcc/config/i386/netbsd64.h
+./gcc/config/i386/netware.h
+./gcc/config/i386/nto.h
+./gcc/config/i386/openbsd.h
+./gcc/config/i386/ptx4-i.h
+./gcc/config/i386/rtemself.h
+./gcc/config/i386/sco5.h
+./gcc/config/i386/sol2-c1.asm
+./gcc/config/i386/sol2-ci.asm
+./gcc/config/i386/sol2-cn.asm
+./gcc/config/i386/sol2-gc1.asm
+./gcc/config/i386/sol2.h
+./gcc/config/i386/svr3.ifile
+./gcc/config/i386/svr3dbx.h
+./gcc/config/i386/svr3gas.h
+./gcc/config/i386/svr3z.ifile
+./gcc/config/i386/sysv3.h
+./gcc/config/i386/sysv4-cpp.h
+./gcc/config/i386/sysv4.h
+./gcc/config/i386/sysv5.h
+./gcc/config/i386/t-beos
+./gcc/config/i386/t-crtpic
+./gcc/config/i386/t-crtstuff
+./gcc/config/i386/t-cygming
+./gcc/config/i386/t-cygwin
+./gcc/config/i386/t-djgpp
+./gcc/config/i386/t-i386elf
+./gcc/config/i386/t-interix
+./gcc/config/i386/t-linux64
+./gcc/config/i386/t-mingw32
+./gcc/config/i386/t-nto
+./gcc/config/i386/t-openbsd
+./gcc/config/i386/t-rtems-i386
+./gcc/config/i386/t-sco5
+./gcc/config/i386/t-sol2
+./gcc/config/i386/t-svr3dbx
+./gcc/config/i386/t-udk
+./gcc/config/i386/t-uwin
+./gcc/config/i386/t-vxworks
+./gcc/config/i386/udk.h
+./gcc/config/i386/uwin.asm
+./gcc/config/i386/uwin.h
+./gcc/config/i386/vsta.h
+./gcc/config/i386/vxworks.h
+./gcc/config/i386/winnt.c
+./gcc/config/i386/x-mingw32
+./gcc/config/i386/xm-cygwin.h
+./gcc/config/i386/xm-djgpp.h
+./gcc/config/i386/xm-mingw32.h
+./gcc/config/i860
+./gcc/config/i960
+./gcc/config/ia64
+./gcc/config/interix.h
+./gcc/config/interix3.h
+./gcc/config/ip2k
+./gcc/config/iq2000
+./gcc/config/kaos.h
+./gcc/config/kfreebsdgnu.h
+./gcc/config/libgcc-glibc.ver
+./gcc/config/libgloss.h
+./gcc/config/linux-aout.h
+./gcc/config/linux.h
+./gcc/config/lynx-ng.h
+./gcc/config/lynx.h
+./gcc/config/m32r
+./gcc/config/m68hc11
+./gcc/config/m68k
+./gcc/config/mcore
+./gcc/config/mips
+./gcc/config/mmix
+./gcc/config/mn10300
+./gcc/config/netbsd-aout.h
+./gcc/config/netbsd-elf.h
+./gcc/config/netbsd.h
+./gcc/config/netware.h
+./gcc/config/ns32k
+./gcc/config/openbsd-oldgas.h
+./gcc/config/openbsd.h
+./gcc/config/pa
+./gcc/config/pdp11
+./gcc/config/ptx4.h
+./gcc/config/rs6000
+./gcc/config/rtems.h
+./gcc/config/s390
+./gcc/config/sh
+./gcc/config/sol2.h
+./gcc/config/sparc
+./gcc/config/stormy16
+./gcc/config/svr3.h
+./gcc/config/svr4.h
+./gcc/config/t-darwin
+./gcc/config/t-freebsd
+./gcc/config/t-freebsd-thread
+./gcc/config/t-gnu
+./gcc/config/t-kfreebsd-gnu
+./gcc/config/t-libc-ok
+./gcc/config/t-libgcc-pic
+./gcc/config/t-libunwind
+./gcc/config/t-linux
+./gcc/config/t-linux-gnulibc1
+./gcc/config/t-netbsd
+./gcc/config/t-openbsd
+./gcc/config/t-openbsd-thread
+./gcc/config/t-rtems
+./gcc/config/t-slibgcc-darwin
+./gcc/config/t-slibgcc-elf-ver
+./gcc/config/t-slibgcc-nolc-override
+./gcc/config/t-slibgcc-sld
+./gcc/config/t-svr4
+./gcc/config/t-vxworks
+./gcc/config/tm-dwarf2.h
+./gcc/config/udivmod.c
+./gcc/config/udivmodsi4.c
+./gcc/config/usegas.h
+./gcc/config/v850
+./gcc/config/vax
+./gcc/config/vxlib.c
+./gcc/config/vxworks.h
+./gcc/config/windiss.h
+./gcc/config/x-interix
+./gcc/config/xtensa
+./gcc/configure
+./gcc/configure.ac
+./gcc/cp/ChangeLog
+./gcc/cp/ChangeLog.1
+./gcc/cp/ChangeLog.2
+./gcc/cp/ChangeLog.3
+./gcc/cp/ChangeLog.egcs
+./gcc/cp/Make-lang.in
+./gcc/cp/NEWS
+./gcc/cp/config-lang.in
+./gcc/f/ChangeLog
+./gcc/f/ChangeLog.0
+./gcc/f/Make-lang.in
+./gcc/f/RELEASE-PREP
+./gcc/f/config-lang.in
+./gcc/fixinc
+./gcc/fixproto
+./gcc/gccbug.in
+./gcc/ginclude
+./gcc/libgcc-darwin.ver
+./gcc/libgcc-std.ver
+./gcc/mkconfig.sh
+./gcc/mkheaders.in
+./gcc/mkinstalldirs
+./gcc/mklibgcc.in
+./gcc/mkmap-flat.awk
+./gcc/mkmap-symver.awk
+./gcc/move-if-change
+./gcc/objc/Make-lang.in
+./gcc/objc/config-lang.in
+./gcc/po
+./gcc/scan-types.sh
+./gcc/sort-protos
+./gcc/treelang
+./include/ChangeLog
+./include/floatformat.h
+./include/fnmatch.h
+./include/getopt.h
+./include/sort.h
+./include/symcat.h
+./include/ternary.h
+./include/xregex.h
+./include/xregex2.h
+./include/xtensa-config.h
+./install-sh
+./intl
+./libf2c
+./libiberty/Makefile.in
+./libiberty/_doprnt.c
+./libiberty/acconfig.h
+./libiberty/aclocal.m4
+./libiberty/alloca.c
+./libiberty/argv.c
+./libiberty/asprintf.c
+./libiberty/atexit.c
+./libiberty/basename.c
+./libiberty/bcmp.c
+./libiberty/bcopy.c
+./libiberty/bsearch.c
+./libiberty/bzero.c
+./libiberty/calloc.c
+./libiberty/clock.c
+./libiberty/config
+./libiberty/config.h-vms
+./libiberty/config.in
+./libiberty/config.table
+./libiberty/config/mh-aix
+./libiberty/config/mh-cxux7
+./libiberty/config/mh-fbsd21
+./libiberty/config/mh-openedition
+./libiberty/config/mh-windows
+./libiberty/configure
+./libiberty/configure.ac
+./libiberty/copying-lib.texi
+./libiberty/copysign.c
+./libiberty/cp-demint.c
+./libiberty/fdmatch.c
+./libiberty/ffs.c
+./libiberty/floatformat.c
+./libiberty/fnmatch.c
+./libiberty/fnmatch.txh
+./libiberty/functions.texi
+./libiberty/gather-docs
+./libiberty/getcwd.c
+./libiberty/getopt.c
+./libiberty/getopt1.c
+./libiberty/getpagesize.c
+./libiberty/index.c
+./libiberty/libiberty.texi
+./libiberty/maint-tool
+./libiberty/makefile.vms
+./libiberty/memchr.c
+./libiberty/memcmp.c
+./libiberty/memcpy.c
+./libiberty/memmove.c
+./libiberty/mempcpy.c
+./libiberty/memset.c
+./libiberty/mkstemps.c
+./libiberty/mpw-config.in
+./libiberty/mpw-make.sed
+./libiberty/mpw.c
+./libiberty/msdos.c
+./libiberty/partition.c
+./libiberty/pex-djgpp.c
+./libiberty/pex-mpw.c
+./libiberty/pex-msdos.c
+./libiberty/pex-os2.c
+./libiberty/pex-win32.c
+./libiberty/pexecute.txh
+./libiberty/putenv.c
+./libiberty/random.c
+./libiberty/regex.c
+./libiberty/rename.c
+./libiberty/rindex.c
+./libiberty/setenv.c
+./libiberty/sigsetmask.c
+./libiberty/snprintf.c
+./libiberty/sort.c
+./libiberty/spaces.c
+./libiberty/stpcpy.c
+./libiberty/stpncpy.c
+./libiberty/strcasecmp.c
+./libiberty/strchr.c
+./libiberty/strdup.c
+./libiberty/strerror.c
+./libiberty/strncasecmp.c
+./libiberty/strncmp.c
+./libiberty/strrchr.c
+./libiberty/strsignal.c
+./libiberty/strstr.c
+./libiberty/strtod.c
+./libiberty/strtol.c
+./libiberty/strtoul.c
+./libiberty/ternary.c
+./libiberty/testsuite
+./libiberty/tmpnam.c
+./libiberty/vasprintf.c
+./libiberty/vfork.c
+./libiberty/vfprintf.c
+./libiberty/vmsbuild.com
+./libiberty/vprintf.c
+./libiberty/vsnprintf.c
+./libiberty/vsprintf.c
+./libiberty/waitpid.c
+./libobjc/Makefile.in
+./libobjc/aclocal.m4
+./libobjc/config.h.in
+./libobjc/configure
+./libobjc/configure.in
+./libobjc/makefile.dos
+./libobjc/thr-decosf1.c
+./libobjc/thr-irix.c
+./libobjc/thr-mach.c
+./libobjc/thr-os2.c
+./libobjc/thr-rtems.c
+./libobjc/thr-solaris.c
+./libobjc/thr-vxworks.c
+./libobjc/thr-win32.c
+./libstdc++-v3/.cvsignore
+./libstdc++-v3/Makefile.am
+./libstdc++-v3/Makefile.in
+./libstdc++-v3/acconfig.h
+./libstdc++-v3/acinclude.m4
+./libstdc++-v3/aclocal.m4
+./libstdc++-v3/config.h.in
+./libstdc++-v3/config/abi
+./libstdc++-v3/config/cpu/alpha
+./libstdc++-v3/config/cpu/cris
+./libstdc++-v3/config/cpu/hppa
+./libstdc++-v3/config/cpu/ia64
+./libstdc++-v3/config/cpu/m68k
+./libstdc++-v3/config/cpu/mips
+./libstdc++-v3/config/cpu/powerpc
+./libstdc++-v3/config/cpu/s390
+./libstdc++-v3/config/cpu/sparc
+./libstdc++-v3/config/locale/gnu
+./libstdc++-v3/config/os/aix
+./libstdc++-v3/config/os/djgpp
+./libstdc++-v3/config/os/gnu-linux
+./libstdc++-v3/config/os/hpux
+./libstdc++-v3/config/os/irix
+./libstdc++-v3/config/os/mingw32
+./libstdc++-v3/config/os/newlib
+./libstdc++-v3/config/os/qnx
+./libstdc++-v3/config/os/solaris
+./libstdc++-v3/config/os/tpf
+./libstdc++-v3/config/os/vxworks
+./libstdc++-v3/config/os/windiss
+./libstdc++-v3/configure
+./libstdc++-v3/configure.ac
+./libstdc++-v3/configure.host
+./libstdc++-v3/crossconfig.m4
+./libstdc++-v3/docs
+./libstdc++-v3/fragment.am
+./libstdc++-v3/libmath/Makefile.am
+./libstdc++-v3/libmath/Makefile.in
+./libstdc++-v3/libsupc++/Makefile.am
+./libstdc++-v3/libsupc++/Makefile.in
+./libstdc++-v3/linkage.m4
+./libstdc++-v3/po
+./libstdc++-v3/scripts
+./libstdc++-v3/src/Makefile.am
+./libstdc++-v3/src/Makefile.in
+./libstdc++-v3/testsuite
+./libtool.m4
+./ltcf-c.sh
+./ltcf-cxx.sh
+./ltcf-gcj.sh
+./ltconfig
+./ltmain.sh
+./maintainer-scripts
+./missing
+./mkdep
+./mkinstalldirs
+./move-if-change
+./symlink-tree
+./ylwrap
diff --git a/contrib/gcc-3.4/README.DRAGONFLY b/contrib/gcc-3.4/README.DRAGONFLY
new file mode 100644 (file)
index 0000000..f1acd61
--- /dev/null
@@ -0,0 +1,52 @@
+
+                       GCC-3.3-20040126 AS USED BY DRAGONFLY
+
+    This directory contains a selected set of files from the gnu 
+    gcc-3.4-20040618 distribution.  The entire distribution is 188MB but
+    we really only need around 31MB of it.  No files have been moved
+    or modified from their extracted position.
+
+    DO NOT CREATE OR EDIT ANY FILES IN THIS DIRECTORY HIERARCHY!  THIS
+    HIERARCHY REPRESENTS AN EXACT COPY, MINUS UNNEEDED FILES, OF THE GNU
+    GCC DISTRIBUTION.  All modifications are made in the 
+    DragonFly build wrapper, in /usr/src/gnu/usr.bin/cc34 and
+    /usr/src/gnu/lib/gcc34, by creating overrides or performing surgery
+    on the distribution.  The only additional files added to this directory
+    are README.DRAGONFLY and README.DELETED. 
+
+       MD5 (gcc-3.4-20040618.tar.bz2) = 6eb0e85c225250cc40b75496419d4250
+
+    UPGRADE PROCDURE:
+
+       * download a new gcc-3.4.X dist greater then 3.4-20040618
+         (the release after this snapshot would be gcc-3.4.1).
+
+       * extract the archive into this directory, overlaying the
+         existing files.
+
+       * A 'cvs update' will show you what has changed ('M') relative 
+         to what we had before.  There will be hundreds of files marked
+         '?' which, if not needed, should be deleted and NOT COMMITTED.
+         If any new files are needed you can cvs add and commit them.
+
+       * Make sure that both buildworld and a crossbuilt buildworld
+         for supported architectures works before committing the upgrade,
+         making adjustments within /usr/src/gnu/usr.bin/cc34.
+
+         DO NOT MAKE ANY EDITS TO THE GCC DISTRIBUTION IN THIS CONTRIB
+         DIRECTORY, OTHER THEN TO ADD OR DELETE FILES ASSOCIATED WITH THE
+         GNU DISTRIBUTION.
+
+    Do not overlay major rev changes in the contrib directory or
+    build infrastructure directory for older major revs!  Create a new
+    major rev directory as contrib/gcc-x.x.  The older major revs in
+    contrib/gcc-x.x can be physically removed from the CVS repository,
+    leaving only this file (README.DRAGONFLY) and README.DELETED in place.
+    Older gcc dists can be recovered by manually unpacking older gnu dists
+    in /usr/src/contrib, without CVS support.  Do not physically remove
+    the DFly build infrastructure for older GCCs from
+    /usr/src/gnu/usr.bin/.  cvs delete, sure, but no physical removal,
+    because then you won't be able to revert your cvs tree past a major
+    rev change.
+
+    The file README.DELETED contains a list of deleted files.
diff --git a/contrib/gcc-3.4/README.SCO b/contrib/gcc-3.4/README.SCO
new file mode 100644 (file)
index 0000000..f86b82b
--- /dev/null
@@ -0,0 +1,27 @@
+As all users of GCC will know, SCO has recently made claims concerning
+alleged copyright infringement by recent versions of the operating
+system kernel called Linux.  SCO has made irresponsible public
+statements about this supposed copyright infringement without
+releasing any evidence of the infringement, and has demanded that
+users of Linux, the kernel most often used with the GNU system, pay
+for a license.  This license is incompatible with the GPL, and in the
+opinion of the Free Software Foundation such a demand unquestionably
+violates the GNU General Public License under which the kernel is
+distributed.
+
+We have been urged to drop support for SCO Unix from this release of
+GCC, as a protest against this irresponsible aggression against free
+software and GNU/Linux.  However, the direct effect of this action
+would fall on users of GCC rather than on SCO.  For the moment, we
+have decided not to take that action.  The Free Software Foundation's
+overriding goal is to protect the freedom of the free software
+community, including developers and users, but we also want to serve
+users.  Protecting the community from an attack sometimes requires
+steps that will inconvenience some in the community.  Such a step is
+not yet necessary, in our view, but we cannot indefinitely continue to
+ignore the aggression against our community taken by a party that has
+long profited from the commercial distribution of our programs.  We
+urge users of SCO Unix to make clear to SCO their disapproval of the
+company's aggression against the free software community.  We will
+have a further announcement concerning continuing support of SCO Unix
+by GCC before our next release.
diff --git a/contrib/gcc-3.4/gcc/COPYING b/contrib/gcc-3.4/gcc/COPYING
new file mode 100644 (file)
index 0000000..d60c31a
--- /dev/null
@@ -0,0 +1,340 @@
+                   GNU GENERAL PUBLIC LICENSE
+                      Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                           Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+\f
+                   GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+\f
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+\f
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+\f
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                           NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                    END OF TERMS AND CONDITIONS
+\f
+           How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/contrib/gcc-3.4/gcc/COPYING.LIB b/contrib/gcc-3.4/gcc/COPYING.LIB
new file mode 100644 (file)
index 0000000..b1e3f5a
--- /dev/null
@@ -0,0 +1,504 @@
+                 GNU LESSER GENERAL PUBLIC LICENSE
+                      Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+                           Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+  This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+not price.  Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+  To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+\f
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License.  This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom.  The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+of an advantage over competing non-free programs.  These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries.  However, the Lesser license provides advantages in certain
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+\f
+                 GNU LESSER GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+  
+  1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+  You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+\f
+  2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library.  To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License.  (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+\f
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+  If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library&q