PATCH (libstdc++-v3): Port testsuite/testsuite_performance.h

[Loren James Rittle]

> I have been told some modern GNU/Linux distributions finally got rid of
> that silly <malloc.h> (which was non-standard and warned about by Borland
> C++ already more than 10 years ago) as well, so wouldn't an autoconf test
> be better?

Unless specially-written, an autoconf test would find a <malloc.h> on
FreeBSD.  However, it will warn on each compilation that malloc.h is
non-standard, etc.

Frankly, I'd rather unconditionally kill it.  This is in test code not
run by most non-developers at this point.  I think we are looking for
a semi- to fully- POSIX way to learn "amount of memory owned by this
process".  Anyone?  (I'd know how to do it for various systems in a
non-standard way.)

Regards,
Loren