End-of-file During Read, Unit -5, File Internal List-directed Read

fortran 90 compiler for linux

 fortran 90 compiler for linux

Writer	Message
	fortran 90 compiler for linux Quote: > I have tried the Intel compiler. > it looks like working, merely render me quite a lot of errors. I'grand > currently runnig some f90 programs that a guy gave to me. The programme > is supposed to piece of work fine, but the compiler doesn't like some syntax, > like the simbol '&' to continue into a new line, or the 'c' to comment. > The real problem, however comes out when I endeavour to link some Numerical > Recipes (fortran 77) routines. The compiler really doesn't like them :( > Is at that place any way to make the compiler more tolerant so I can utilise it > with the routine I have at my disposal? I installed Intel'southward f90/95 compiler years ago and it works like a charm. The source files should be called *.f90. The compiler is less tolerant of some kinds of errors than some other compilers. Due east.g. I had to edit programs in which I had a comma between WRITE and the list to be written. Good for me to be reminded. It also gives me annoying Warnings about page feeds I like to put in for a ameliorate legible print-out of programs with subroutines, but I can suppress these warnings. -- Dieter Britz,   Kemisk Institut, Aarhus Universitet, Danmark.
Tue, 01 Jan 2008 15:04:02 GMT
beliav.. #17 / 25	fortran xc compiler for linux Quote: > I installed Intel's f90/95 compiler years agone and information technology works like > a charm. The source files should exist called *.f90. The Intel compiler, like most other compilers, (1) treats *.f90 files by default every bit having costless source form (ii) treats *.f and *.for files equally having stock-still source form (iii) has compiler options to override these rules and force a file to be treated as free or stock-still.
Tue, 01 Jan 2008 18:57:16 GMT
beliav.. #eighteen / 25	fortran 90 compiler for linux Quote: > > On 13 Jul 2005 13:46:33 -0700, "Chris Hulbert" > >>Try gfortran or g95 > > Are they consummate and standard-conforming? > At that place is no complete and standard-conforming > Fortran compiler :-). I don't know of any outstanding bugs in the Lahey/Fujitsu Fortran 95 compiler for Windows, version seven.i in implementing the Fortran 95 standard. The few complaints I have seen almost LF95 in this newsgroup concern some Technical Reports that followed the F95 standard. I wonder if anyone has a counterexample.
Tue, 01 Jan 2008 xix:eleven:58 GMT
Steve.Mor.. #19 / 25	fortran 90 compiler for linux Well, the intel compiler is working now. I had installed it on a remote machine previously, and that gave the problems I already mentioned... I have installed on my desktop at present, and information technology's working fine :))) It that due to the fact I was working remotely?!? It compiles without errors and warning, simply withal information technology doesn't run.... I'chiliad quite a newby, but hither is what I practise : 1) I declare the arrays to be dynamically allocated:  integer n real, dimension(:), allocatable :: cz,apm real*viii, dimension(:), allocatable :: al8,del8 2) I read a file (input.in) where I set a lot of parameters and also the name of the file I want to open up open(20,file='input.in',status='old',grade='formatted') read(20,'(a)') slicein           ! input file read(20,*) ah1,am1,as1    ! various parameter I set .... where the file input.in has the post-obit form table.ascii 8 0 0 .... 3) So I read the file table.ascii where the data are stored  open up (20,file=slicein,status='old',class='unformatted') read (20) n   allocate (cz(ngal),apm(ngal)) allocate (al8(ngal),del8(ngal)  read (twenty) al8, del8, cz, apm close(20) However, the program encounter a problem exactly earlier the signal read (20) north        to a higher place and return me this foreign list forrtl: severe (39): fault during read, unit of measurement 20, file /home/myfold/table.ascii Epitome       PC             Routine          Line            Source scarlet          080A6F18  Unknown        Unknown  Unknown blood-red          080A6A10  Unknown        Unknown  Unknown red          0807B081   Unknown       Unknown  Unknown red          0805AE20  Unknown        Unknown  Unknown cherry-red          0805B2C3  Unknown        Unknown  Unknown cerise          08067F98   Unknown        Unknown  Unknown red          0804B317  Unknown         Unknown  Unknown ruby-red          0804A3C8  Unknown        Unknown  Unknown Unknown   40090D17  Unknown    Unknown  Unknown blood-red          0804A281  Unknown         Unknown  Unknown (ruby is the name of the executable file) I'm quite sure the error is something very obvious, only I cannot figure information technology out. Whatever help? Thank you a lot! S.
Tue, 01 Jan 2008 21:27:17 GMT
Tim Princ #xx / 25	fortran 90 compiler for linux Quote: > Well, the intel compiler is working now. > I had installed it on a remote machine previously, and that gave the > problems I already mentioned... > I have installed on my desktop now, and it'southward working fine :))) > Information technology that due to the fact I was working remotely?!? > It compiles without errors and alarm, but still information technology doesn't run.... > I'thou quite a newby, only here is what I practice : > 1) I declare the arrays to be dynamically allocated: >  integer n >  real, dimension(:), allocatable :: cz,apm >  real*viii, dimension(:), allocatable :: al8,del8 > two) I read a file (input.in) where I set a lot of parameters and also > the name of the file I want to open up > open up(20,file='input.in',status='old',form='formatted') > read(20,'(a)') slicein              ! input file > read(20,*) ah1,am1,as1    ! diverse parameter I set > .... > where the file input.in has the post-obit class > tabular array.ascii > 8 0 0 > .... > 3) Then I read the file table.ascii where the data are stored >  open up (20,file=slicein,status='onetime',form='unformatted') >  read (20) n >   allocate (cz(ngal),apm(ngal)) >   allocate (al8(ngal),del8(ngal) >  read (20) al8, del8, cz, apm >  close(xx) > Withal, the program run across a problem exactly before the bespeak > read (20) n        above and render me this strange listing > forrtl: severe (39): error during read, unit 20, file > /abode/myfold/tabular array.ascii > Epitome       PC             Routine          Line            Source > cerise          080A6F18  Unknown        Unknown  Unknown > red          080A6A10  Unknown        Unknown  Unknown > cherry-red          0807B081   Unknown       Unknown  Unknown > red          0805AE20  Unknown        Unknown  Unknown > red          0805B2C3  Unknown        Unknown  Unknown > red          08067F98   Unknown        Unknown  Unknown > red          0804B317  Unknown         Unknown  Unknown > reddish          0804A3C8  Unknown        Unknown  Unknown > Unknown   40090D17  Unknown    Unknown  Unknown > cerise          0804A281  Unknown         Unknown  Unknown > (red is the proper noun of the executable file) > I'g quite sure the error is something very obvious, simply I cannot effigy > it out. Any assist? Sequential unformatted is a fairly special file format, non one which would work with a text editor, nor exist portable in general fifty-fifty amidst Fortran compilers.  'unformatted' is non the same every bit the more contempo (since thirty years ago) list directed formatted, which you may have meant to utilise.
Tue, 01 Jan 2008 22:05:07 GMT
Herman D. Knobl #21 / 25	fortran ninety compiler for linux Pleaes be patient with me every bit I go on my sometime soap box. First, Information technology is not possible to testify that a non-piffling program is correct. It's undecidable. Therefore there are bugs in every non-trivial plan; and a compiler surely fills the definition of a non-trivial program. So all compilers have bugs. Some are known, some are not. Some could reflect Standard misinterpretations, although I too am not aware of whatever. In the case of commercial compilers like Lahey LF95, PathScale PATHF90 and Intel IFORT,and Silverfrost (formally Salford) FTN95, information technology has been my experience that reported (well documented) bugs, Standards related or not, are taken quite seriously, acknowledged and fixed, if possible without introducing more bugs, in reasonably curt society (typically adjacent release or via a "fixed" module that the development team ofttimes offers to send to the bug originator). This said, at this point in history, again I agree with you. That is, for the most office most Fotran compilers are reasonably stable and usable most oft without running into bugs, and less often running into bugs related to Fortran 90 Standards, and probably even less frequently related to Fortran 95 Standards. For the sake of Fortran application integrity, we all the same demand to work with compiler developers so that when we employ their compilers to generate applicatons (all applicatoins are "mission critical" in my stance), those applications have as much integrity ("soundness") as humanly possible. (That's why good debugging options like Salford and Lahey's uninitialized variables, subscript/string ranges, etc. are then important. Skip Knoble -|> -|> > On thirteen Jul 2005 xiii:46:33 -0700, "Chris Hulbert" -|> > -|> > -|> >>Try gfortran or g95 -|> > -|> > -|> > Are they complete and standard-conforming? -|> -|> There is no complete and standard-conforming -|> Fortran compiler :-). -| -|I don't know of any outstanding bugs in the Lahey/Fujitsu Fortran 95 -|compiler for Windows, version 7.1 in implementing the Fortran 95 -|standard. The few complaints I have seen about LF95 in this newsgroup -|concern some Technical Reports that followed the F95 standard. I wonder -|if anyone has a counterexample.
Tue, 01 Jan 2008 22:06:52 GMT
James Van Buskir #22 / 25	fortran 90 compiler for linux Quote: > I don't know of any outstanding bugs in the Lahey/Fujitsu Fortran 95 > compiler for Windows, version seven.one in implementing the Fortran 95 > standard. The few complaints I have seen nearly LF95 in this newsgroup > concern some Technical Reports that followed the F95 standard. I wonder > if anyone has a counterexample. I have seen sufficient bugs in previous versions to be fairly certain that the bugs must exist there in the current version.  What does LF95 7.1 exercise about http://abode.comcast.internet/~kmbtib/Fortran_stuff/elem_assign.f90 for example?  If y'all utilise any compiler as your primary evolution compiler for a while you lot are going to run across bugs.  The f95 standard itself has bugs and internal contradictions and I have no idea how you could create a standard for which this would non be the case.  How can you write a bug-costless compiler to an inconsistent standard? -- write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, & half dozen.0134700243160014d-154/),(/'x'/)); cease
Wed, 02 Jan 2008 00:forty:00 GMT
Paul Van Dels #23 / 25	fortran xc compiler for linux Quote: >>I don't know of any outstanding bugs in the Lahey/Fujitsu Fortran 95 >>compiler for Windows, version vii.ane in implementing the Fortran 95 >>standard. The few complaints I have seen about LF95 in this newsgroup >>business concern some Technical Reports that followed the F95 standard. I wonder >>if anyone has a counterexample. > I have seen sufficient bugs in previous versions to exist adequately sure > that the bugs must be in that location in the electric current version.  What does LF95 seven.i > practise most > http://dwelling.comcast.net/~kmbtib/Fortran_stuff/elem_assign.f90 Dunno about the windows 7.1, but the unix 6.2c does the post-obit: lnx:scratch : lf95 blah.f90 Encountered 0 errors, 0 warnings in file blah.f90. lnx:scratch : a.out original x =  7 11 13 permuted x =  11 13 seven new x =  xi thirteen xi And v8.1 intel: lnx:scratch : ifort -static-libcxa apathetic.f90 lnx:scratch : a.out original x =            7          11          13 permuted x =           eleven          xiii           seven new 10 =           11          13          11 g95 seems to get it correct though (at least I think and then): lnx:scratch : g95 blah.f90 lnx:scratch : a.out original x =  7 xi 13 permuted ten =  11 xiii 7 new 10 =  11 thirteen 7 cheers, paulv -- Paul van Delst
Wednesday, 02 Jan 2008 00:54:28 GMT
James Van Buskir #24 / 25	fortran 90 compiler for linux Quote: > g95 seems to get information technology right though (at to the lowest degree I think then): Yeah, Andy wrote me a note a while dorsum to let me know that he had stock-still this bug.  It is and then amusing that both LF95 and ifort take the same fault here.  Even surrounding the dexter of the assignment with parentheses doesn't help these compilers out! -- write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, & 6.0134700243160014d-154/),(/'10'/)); terminate
Wed, 02 Jan 2008 01:00:59 GMT
Steve Lione #25 / 25	fortran 90 compiler for linux On Fri, 15 Jul 2005 eleven:00:59 -0600, "James Van Buskirk" Quote: >> g95 seems to become information technology right though (at least I think so): >Yes, Andy wrote me a note a while back to permit me know that >he had fixed this bug.  Information technology is so amusing that both LF95 and >ifort have the same fault here.  Fifty-fifty surrounding the dexter >of the consignment with parentheses doesn't help these >compilers out! Now that it has been brought to our attention, we'll fix it too. Steve Lionel Software Products Division Intel Corporation Nashua, NH User communities for Intel Software Development Products http://softwareforums.intel.com/ Intel Fortran Support http://developer.intel.com/software/products/support/
Wed, 02 Jan 2008 03:31:32 GMT

Page 2 of two

[ 25 post ]

Go to page: [1] [2]

Powered past phpBB® Forum Software

parkerdebut1961.blogspot.com

Source: http://computer-programming-forum.com/49-fortran/4f2e00dc99898a2e-2.htm