https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80850
--- Comment #2 from DIL <liakhdi at ornl dot gov> --- I have fixed all issues reported by VALGRIND so the code now is valgrind-clean. However, the problem I reported still shows up from time to time (only when the code is compiled with -g and no optimization: BUILD_TYPE = DEV). The test which fails depends on a number of source files, so I do not really see a clear way to localize the problem in a small code snippet. In fact, the ALLOCATE() statement which fails works just fine when called from other places. I thought you might have some tools to inspect the ALLOCATE() code to see why it sees a NULLIFIED pointer as ALLOCATED when the error message is triggered (the exact location of the ALLOCATE statement is specified in the previous message). But I am not sure how hard this would be. Also, I haven't had a chance to try the new 7.1 compiler. Thanks, Dmitry
