Re: Salford compiler: Assigning a value to a constant expression is invalid
From: Herman D. Knoble (SkipKnobleLESS_at_SPAMpsu.edu)
Date: 02/04/04
- Next message: Richard Maine: "Re: DO loop standards question."
- Previous message: Jason: "Re: Is this standard f90?"
- In reply to: Bil Kleb: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Next in thread: Bil Kleb: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Reply: Bil Kleb: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Reply: Richard Maine: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 04 Feb 2004 10:32:31 -0500
One can appreciate the complexities involved. However, when encountering
a bug, it is not usually wise, I think, to assume that it's a compiler bug.
I recently worked with a professor here on a nuclear reactor simulator
package by ORNL. This was about 80,000+ lines of code and it had
three misspelt variable names as fleshed out by Salford FTN95 /Checkmate
and verified by Lahey LF95 with debug options. This multiple compiler testing
showed that there were other platform dependent problems and three subscritps
out of range. We were able to work with ORNL and fix each these (known) bugs
and the resultant code compiled and ran using both of the above compilers
in full debug mode.
Over the past 35 years I've worked with many large codes like
this. Some were government (NASA) codes, others were "Lab"
and other private codes.
To be honest, many of these codes were very messy. I doubt that is
the case with your code, but your code may call code that you did not
write. In our case, we found all these large codes had some semantic errors.
Moreover the authors involved did not want to hear this kind of news.
Only on rare occasion did we report to the compiler vendor a compiler bug.
Finally, I do not think my experience over the years is unique.
For what it's worth.
Skip
On Wed, 04 Feb 2004 09:50:12 -0500, Bil Kleb <Bil.Kleb@NASA.Gov> wrote:
-|Herman D. Knoble wrote:
-| >
-|> I'd suggest submitting a self-contained source code file to Salford Support.
-|> It's darn difficult to fix bugs that are reported only in code segments.
-|
-|Agreed, that would be best.
-|
-|However, this is deep in an export-restricted code and, as I am sure
-|your are aware, it is very time consuming to create stripped-down,
-|self-contained source which exhibits the same problem. I recently tried
-|that for a NAG bug and gave up. However, since NAG has U.S.-based support,
-|they were able to request the code (http://fun3d.larc.nasa.gov) so that
-|I could ship them source. The initial response was that even they
-|have not been able to strip the problem down to something simple.
-|
-|I was lucky with the first of three Salford bugs I found: It was in one
-|of our low-level (i.e., releasable), self-contained library routines and
-|furthermore, it was developed test-first using our Fortran unit testing
-|framework. So all I had to do in that case was send the routine and
-|the test routine. They had a fix in less than a week.
-|
-|> If you post such a compilable/runable source code we the Fortran community
-|> can test it on several platforms which might help further document your problem.
-|
-|We already test nightly on seven platforms/compilers as the large grain part
-|of our Continuous Integration practice.
-|
-|Regards,
Herman D. (Skip) Knoble, Research Associate
(a computing professional for 38 years)
Email: SkipKnobleLESS@SPAMpsu.edu
Web: http://www.personal.psu.edu/hdk
Penn State Information Technology Services
Academic Services and Emerging Technologies
Graduate Education and Research Services
Penn State University
214C Computer Building
University Park, PA 16802-21013
Phone:+1 814 865-0818 Fax:+1 814 863-7049
- Next message: Richard Maine: "Re: DO loop standards question."
- Previous message: Jason: "Re: Is this standard f90?"
- In reply to: Bil Kleb: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Next in thread: Bil Kleb: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Reply: Bil Kleb: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Reply: Richard Maine: "Re: Salford compiler: Assigning a value to a constant expression is invalid"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
