Just tried giving Crypto++ 5.0 a try on a linux system using Red Hat's gcc 2.96 and it seems it doesn't like bench.cpp much at all. Everything else compiles fine, but when the make process gets to bench.cpp, the compiler goes nuts and starts sucking up all available memory and swap space until it explodes. After letting it sit for about 30 seconds, the cc1plus process has consumed pretty much all memory on my system (top shows it as having used 210 MB of physical memory, and it just keep using more).
Eventually, I'm assuming it will just consume all available memory and die, but I ^C it before it happens. In any event, bench.cpp won't compile. I noticed this happened with Crypto++ 4.2 and Red Hat's gcc 2.96 if you use -O2 in CXXFLAGS. Anyway, is this a compiler bug? I'm assuming so, and if so, is there anything that can be done about it? Thanks. J
