Libgcc symbols

[Gabriel Dos Reis]

| > Why we still have libio in-tree at all is another question.  (I have
| > never understood why iostreams aren't a layer of paint on top of
| > the public stdio interface.)

Because, we don't want to tie C++ IOstreams performance to that of C
stdio on all plateforms.  We would like to have decent I/O performance
wherever possible.  libio is one way to to do, it is certainly not the
best one; but I don't agree with implementations of C++ IOstreams on
top of C stdio.  What we have now inV3 is a short-term solution
because of some obscure implementation problems with libio.  There are
alternative schemes such as Matt Austern's implementation which worths
consideration.

-- Gaby