This isn't a problem, per se, but in trying to gather more information for one of the infamous "catastrophic internal errors", I ran ifort 12.0.0 (and its descendants) through valgrind. ifort had several dozen memory access errors (mostly jump-based-on-uninitialized), and fortcom had over 1,000 errors reported (mostly use of uninitialized variables). You guys might want to consider adding memory profiling tests to your pre-release software qualification suite.
