What does that really mean?
How can a compiler put out a message during compilaiton and there is no document that describes that message?
Are the developers all gone and Intel merely sells a shell?
Who at Intel said that?
See https://software.intel.com/en-us/articles/intel-fortran-compiler-diagnostics - linked in the FAQ.
Many of the messages have detailed descriptions, though many do not. If there's a particular one you need help with, let me know.
Well, many of the messages are supposed to be self-descriptive. In particular, there's been an effort to make the diagnostics in the optimization report more understandable to non-specialists. Examples have also been created for some of the more common diagnostics, see https://software.intel.com/en-us/articles/intel-fortran-15-vectorization-diagnostics
Diagnostics issued by the Fortran run-time library are documented in the "List of Run-Time Error Messages" section of the Fortran Compiler User Guide, see for example https://software.intel.com/en-us/node/579769. Other entries under :Handling Run-Time Errors" might also be of interest.
Other parts of the compiler end can potentially issue a very large number of diagnostics, many of which are very rare. Only some of the more common ones have supplementary documentation. Is there a particular diagnostic with which you need help? Can you provide a code sample that causes it? We'll be happy to help, and to add a corresponding online entry.