I was going to contribute to this thread, but Toon Moene said just about
everything I would say.
I'll affirm that it is useless to ask a compiler vendor "do you know of
problems in this area?" Whether or not we do, it is almost always the case
that it takes a particular combination of program usage to bring out a bug.
Unless we see the source and can reproduce the problem ourselves, we can't
tell you if it's a known problem, a new problem, nor what a possible
workaround is. Besides, it is often the case that a user guesses wrong as
to where the problem actually lies.
Don't waste our time and yours by sending us program fragments, pseudocode
or paraphrased error messages. We'll just ask you for a reproducible
example anyway, so as Toon says, you may as well send it first off. Of
course, we do appreciate the smallest possible example, but if you can't
reduce it, then we'll take whatever you've got. Of course, be sure to
include the exact compiler version and the OS you're using (as a
multiplatform vendor, I've lost count of the number of problem reports we
get that just say "Fortran".) The more detail, the better.
Speaking for Compaq Fortran only, we are glad to receive problem reports
from anyone using our products, whether or not you have a "formal
relationship" with us. You're our customers. We'll analyze the problem and
let you know what's wrong, and if there's a fix or workaround available (or
what's wrong with your code!) Of course, customers with support contracts
can get advance updates, but everyone at least gets a helpful response.
And, of course, you get the knowledge that the sooner we learn about a
problem, the sooner it gets fixed for everyone. (Don't wait for a new
release to "see if it's fixed" - you may push out the time for the fix past
the next release.)
For Compaq Fortran support options, see
http://www.compaq.com/fortran/support
Steve Lionel
Compaq Fortran Engineering
http://www.compaq.com/fortran
|