failing test cases

[Loren James Rittle]

Now that I have my population of daily testers up and running again,
I'm looking at 3.3.X and mainline failures.  For the record: On
alpha-freebsd5.2 (3.3) and i386-freebsd5.2 (mainline), most current
libstdc++-v3 failures appeared due to "in malloc(): error: allocation
failed" (then abort() called instead of returning NULL; the systems
are in a debug mode; but I can override it at the per-user level).
sparc64-freebsd5.2 (3.3) didn't fail the tests.  I have addressed it.

Other minor character class (wchar/char) issues appear to have cropped
up (perhaps due to new tests).  Everything else looks as expected, if
not perfect (27_io/filebuf_members.cc and 27_io/filebuf_virtuals.cc
tend to hang/timeout but never on mainline on my desktop).  I'll
attempt to understand and fix these ASAP.  As usual, apologies for the
meager "life-support only" time I'm currently allocating to libstdc++...

Regards,
Loren