forums.silverfrost.com

Do you have an estimate for the size of the reproducer?

I do not think that at this point you can rule out bugs in the source code and conclude that it is only the 32-bit optimiser that is at fault ...

If the program is compiled, this should check compatibility between the routine and interface definition and when the subroutine is compiled a kind incompatibility should be identified. Unfortunatel ...

The compiler does check for mismatched interfaces when possible. In particular, if no explicit interface is required (by the rules of the language), and the mismatched interfaces are in the same sourc ...

Rather than going the C preprocessor route, I think that the better solution to obtaining the compiler version, etc., is to use the F2008 intrinsics COMPILER_VERSION() and COMPILER_OPTIONS(), which ar ...

The code posted by you at Dropbox is not valid Fortran source.

1. Replace tab characters (Ascii 9) by the appropriate number of spaces and ensure that the modified source code follows Fortran fixed ...

The first line contains an inappropriate ',' before 'FILE1'. The second line contains more leading blanks than needed, and extends beyond column 72.

You can use '*' in declaration statements only f ...

The link that John S. gave is for G95, not Gfortran.

G95 is outdated and lacks many of the Fortran 2003 and 2008 features that are present in Gfortran. G95 does not support X64 on Windows, and may ...

... isn't the point of compiler error messages that you can go away and resolve the problem in the Fortran source code, not to change your compiler? (Unless, of course, the error message was bogus). ...

Dan, I think that for running Gfortran the easiest way is to find a Linux system with Gfortran installed on it. A Linux VM on Windows will do almost as well.

You can obtain Gfortran for Windows fro ...

Paul, the example code made be curious, and I find that the 8.40 compiler fails to compile the following variation of the same code:
PROGRAM prog1
IMPLICIT NONE
!
INTEGER, PARAMETER :: VN= ...

The bug is in the fgetc code in salflibc64.dll. Ten instructions before the RET instruction of fgetc(), we see

000000001C009315 movsx r15,byte ptr [rsp+20h] ; sign bit got extended ...

I have done some testing of 85 million values on 2.8ghz i5.

If the numbers are only slightly out of sequence:
do i = 1,n
call random_number(real_array(i))
real_array(i) = real_array(i) + rea ...

Consider the following code, which is in error on Line-6 since the variable on the left and the expression on the right have different shapes.
program nph
implicit none
integer i,ijk,ia(1), ...

Without seeing your source code, I can only speculate. I doubt that the following description has any relevance to your code, but it is illustrative.

The hex representation of -1828645786 is 930114 ...

Do you use any 8-byte integers and do arithmetic on 8 byte integers in your code? If so, note that code compiled with FTN95-32 bit uses X87 instructions for such arithmetic, whereas FTN95-64 uses SSE2 ...