Re: Patch: for libstdc++/2071 test case

[Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>]

Hey, what do you know?  With the mystery of libstdc++/2071 at least
partially solved, the most library-demanding small program I ever
wrote against libstdc++-v2 (it solves crypto-addition problems [1] in
147 NCLOC [2] using a pigeon-hole, brute-force method) using only the
standard parts, final header names and, at the time, the useless std
namespace qualification now compiles and works correctly against
libstdc++-v3 without any changes.

Unfortunately, on the exact same hardware, it now takes 6 times as
long to compile and about twice as long to run (so much for "only
paying for the language features that you use" which is suppose to be
a main tenet of C++ ;-).  On the bright side (for us), it is CPU-bound
and mainly exercises the STL part of the standard C++ library thus it
is unclear that the runtime issue is a libstdc++-v3 issue per se (at
least the part of code that GNU adds).

Regards,
Loren

[1] I.e. ; echo 'the + earth + venus + saturn + uranus = neptune' | time a.out

[2] There actually were comments and white space.
    Counted with: grep -v '^//' word-number.C|grep -v '^$' | wc