FW: Question concerning move from 32bit to 64bit Fortran Code

Navarro, Sylvia snavarro@harris.com
Tue Nov 1 20:01:00 GMT 2005


 -----Original Message-----
From: 	Navarro, Sylvia  
Sent:	Tuesday, November 01, 2005 2:59 PM
To:	'gcc@gcc.gnu.org'
Subject:	Question concerning move from 32bit to 64bit Fortran
Code

I am currently using RedHatLinux4.0, which comes with gcc4.02 on an HP
Opteron and also using g95 (instead of gfortran, due to our algorithm
house).  
'uname -a' produces:
Linux gamma0019 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:00:54 EDT 2005
x86_64 x86_64 x86_64 GNU/Linux

I have received Fortran/C code that works perfectly on an HPi386 (when
using a flag of '-fendian=big', due to the nature of the input file).
Upon trying to compile and run the program on the Opteron, I run into
Fortran I/O errors.  When using the '-fendian =big', the error reads:

[snavarro@gamma0019 hes-version-1.1]$ bin/hesCC
etc/alg_directives.rp.goes  etc/alg_directives.rp.goes  Regression
Retrieval Turned On  IR Sensor Physical Retrieval Turned On  call
getsolar  solar function not used  call getod At line 160 of file
oss_ir_module.f90 (Unit 50
"src/hes/database/oss/linux/selGOES_650-2250.flt.cmpr.swap  ")
Traceback: (Innermost first)
   Called from line 85 of file oss_ir_module.f90
   Called from line 183 of file f90/ooRETR.f90
   Called from line 14 of file f90/fcalls.f90
Fortran runtime error: Reading more data than the record size (RECL)

If I swich the flag to read '-fendian=little', I get a different error: 

[snavarro@gamma0019 hes-version-1.1]$ bin/hesCC
etc/alg_directives.rp.goes  etc/alg_directives.rp.goes  Regression
Retrieval Turned On  IR Sensor Physical Retrieval Turned On  call
getsolar  solar function not used  call getod At line 160 of file
oss_ir_module.f90 (Unit 50
"src/hes/database/oss/linux/selGOES_650-2250.flt.cmpr.swap  ")
Traceback: (Innermost first)
   Called from line 85 of file oss_ir_module.f90
   Called from line 183 of file f90/ooRETR.f90
   Called from line 14 of file f90/fcalls.f90
Fortran runtime error: Corrupt record in unformatted sequential-access
file

I have looked at the g95 manual and found no help there.  I stumbled
across your help forum (topic: Re: 64 bit fortran unformatted on Opteron
-- incompatible with32unformatted) during a search on Google.

I have read the 6 postings concerning this exact issue.  Can you
re-explain how one would go about fixing or working around this problem?

Thank you,
Sylvia Navarro
Software Engineer
HARRIS Corp 
GCSD Civil BU
R5, A115F
321-309-7350

CONFIDENTIALITY NOTICE: THIS EMAIL AND ANY ATTACHMENTS MAY CONTAIN
MATERIAL THAT IS "HARRIS PROPRIETARY INFORMATION", CONFIDENTIAL,
PRIVILEGED, AND/OR ATTORNEY WORK PRODUCT FOR THE SOLE USE OF THE
INTENDED RECIPIENT. ANY REVIEW, RELIANCE, DISTRIBUTION, DISCLOSURE, OR
FORWARDING WITHOUT EXPRESSED PERMISSION IS STRICTLY PROHIBITED.  IF YOU
ARE NOT THE INTENDED RECIPIENT, PLEASE CONTACT THE SENDER AND DELETE ALL
COPIES WITHOUT READING, PRINTING, OR SAVING IN ANY MANNER.  THANK YOU.



More information about the Fortran mailing list