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

fortran ninety compiler for linux

 fortran 90 compiler for linux

Author	Bulletin
	fortran xc compiler for linux Quote: > I have tried the Intel compiler. > information technology looks like working, simply render me quite a lot of errors. I'm > currently runnig some f90 programs that a guy gave to me. The program > is supposed to work fine, but the compiler doesn't like some syntax, > like the simbol '&' to go on into a new line, or the 'c' to comment. > The existent problem, withal comes out when I try to link some Numerical > Recipes (fortran 77) routines. The compiler really doesn't similar them :( > Is there any fashion to make the compiler more tolerant so I can use it > with the routine I have at my disposal? I installed Intel'south f90/95 compiler years ago and it works similar a charm. The source files should be called *.f90. The compiler is less tolerant of some kinds of errors than another compilers. East.one thousand. I had to edit programs in which I had a comma betwixt WRITE and the list to be written. Practiced for me to be reminded. It also gives me annoying Warnings virtually page feeds I similar to put in for a better legible print-out of programs with subroutines, but I can suppress these warnings. -- Dieter Britz,   Kemisk Institut, Aarhus Universitet, Danmark.
Tue, 01 Jan 2008 fifteen:04:02 GMT
beliav.. #17 / 25	fortran ninety compiler for linux Quote: > I installed Intel'south f90/95 compiler years ago and information technology works like > a amuse. The source files should be chosen *.f90. The Intel compiler, similar nearly other compilers, (i) treats *.f90 files past default as having gratis source grade (2) treats *.f and *.for files as having fixed source course (3) has compiler options to override these rules and strength a file to be treated as free or fixed.
Tue, 01 Jan 2008 eighteen:57:16 GMT
beliav.. #18 / 25	fortran xc compiler for linux Quote: > > On 13 Jul 2005 thirteen:46:33 -0700, "Chris Hulbert" > >>Endeavor gfortran or g95 > > Are they consummate and standard-conforming? > There is no consummate and standard-conforming > Fortran compiler :-). I don't know of any outstanding bugs in the Lahey/Fujitsu Fortran 95 compiler for Windows, version vii.1 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.
Tue, 01 Jan 2008 19:11: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 now, and it's working fine :))) It that due to the fact I was working remotely?!? It compiles without errors and alert, merely still information technology doesn't run.... I'm quite a newby, simply hither is what I practise : one) I declare the arrays to exist dynamically allocated:  integer n existent, dimension(:), allocatable :: cz,apm real*8, 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='sometime',form='formatted') read(20,'(a)') slicein           ! input file read(xx,*) ah1,am1,as1    ! various parameter I set .... where the file input.in has the post-obit form table.ascii viii 0 0 .... 3) And then I read the file tabular array.ascii where the data are stored  open (20,file=slicein,status='old',form='unformatted') read (20) northward   allocate (cz(ngal),apm(ngal)) allocate (al8(ngal),del8(ngal)  read (20) al8, del8, cz, apm close(20) However, the plan run across a problem exactly earlier the point read (20) n        above and return me this foreign list forrtl: severe (39): error during read, unit 20, file /home/myfold/table.ascii Epitome       PC             Routine          Line            Source red          080A6F18  Unknown        Unknown  Unknown red          080A6A10  Unknown        Unknown  Unknown 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 cerise          0804A3C8  Unknown        Unknown  Unknown Unknown   40090D17  Unknown    Unknown  Unknown red          0804A281  Unknown         Unknown  Unknown (ruddy is the proper noun of the executable file) I'g quite sure the error is something very obvious, just I cannot figure information technology out. Whatsoever assistance? Thank you a lot! South.
Tue, 01 Jan 2008 21:27:17 GMT
Tim Princ #20 / 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's working fine :))) > It that due to the fact I was working remotely?!? > It compiles without errors and warning, only nonetheless it doesn't run.... > I'm quite a newby, but here is what I do : > 1) I declare the arrays to exist dynamically allocated: >  integer n >  real, dimension(:), allocatable :: cz,apm >  existent*8, dimension(:), allocatable :: al8,del8 > 2) I read a file (input.in) where I set a lot of parameters and as well > the name of the file I want to open > open(twenty,file='input.in',status='old',form='formatted') > read(20,'(a)') slicein              ! input file > read(20,*) ah1,am1,as1    ! various parameter I fix > .... > where the file input.in has the following grade > table.ascii > 8 0 0 > .... > 3) Then I read the file table.ascii where the data are stored >  open (twenty,file=slicein,condition='onetime',form='unformatted') >  read (20) n >   allocate (cz(ngal),apm(ngal)) >   classify (al8(ngal),del8(ngal) >  read (20) al8, del8, cz, apm >  close(20) > Yet, the program encounter a problem exactly before the point > read (20) due north        above and return me this strange list > forrtl: severe (39): error during read, unit 20, file > /home/myfold/table.ascii > Image       PC             Routine          Line            Source > red          080A6F18  Unknown        Unknown  Unknown > crimson          080A6A10  Unknown        Unknown  Unknown > red          0807B081   Unknown       Unknown  Unknown > ruby-red          0805AE20  Unknown        Unknown  Unknown > red          0805B2C3  Unknown        Unknown  Unknown > carmine          08067F98   Unknown        Unknown  Unknown > red          0804B317  Unknown         Unknown  Unknown > blood-red          0804A3C8  Unknown        Unknown  Unknown > Unknown   40090D17  Unknown    Unknown  Unknown > red          0804A281  Unknown         Unknown  Unknown > (red is the proper name of the executable file) > I'k quite certain the error is something very obvious, but I cannot figure > information technology out. Any help? Sequential unformatted is a fairly special file format, not i which would work with a text editor, nor be portable in general fifty-fifty among Fortran compilers.  'unformatted' is not the same as the more contempo (since 30 years ago) list directed formatted, which you may accept meant to use.
Tue, 01 Jan 2008 22:05:07 GMT
Herman D. Knobl #21 / 25	fortran ninety compiler for linux Pleaes exist patient with me as I get on my quondam lather box. Starting time, Information technology is not possible to bear witness that a not-footling program is correct. It's undecidable. Therefore there are bugs in every not-trivial program; and a compiler surely fills the definition of a non-trivial program. So all compilers have bugs. Some are known, some are non. Some could reflect Standard misinterpretations, although I too am non aware of any. In the case of commercial compilers similar Lahey LF95, PathScale PATHF90 and Intel IFORT,and Silverfrost (formally Salford) FTN95, it 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 short club (typically next release or via a "fixed" module that the development squad often offers to send to the bug originator). This said, at this signal in history, again I agree with y'all. That is, for the well-nigh part nigh Fotran compilers are reasonably stable and usable most often without running into bugs, and less frequently running into bugs related to Fortran 90 Standards, and probably fifty-fifty less often related to Fortran 95 Standards. For the sake of Fortran awarding integrity, nosotros still need to work with compiler developers so that when we use their compilers to generate applicatons (all applicatoins are "mission critical" in my stance), those applications accept every bit much integrity ("soundness") equally humanly possible. (That'south why good debugging options similar Salford and Lahey'south uninitialized variables, subscript/string ranges, etc. are and then important. Skip Knoble -|> -|> > On thirteen Jul 2005 13:46:33 -0700, "Chris Hulbert" -|> > -|> > -|> >>Try gfortran or g95 -|> > -|> > -|> > Are they consummate and standard-conforming? -|> -|> There is no complete and standard-befitting -|> 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 -|business 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 7.1 in implementing the Fortran 95 > standard. The few complaints I accept seen about 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 exist fairly sure that the bugs must exist at that place in the electric current version.  What does LF95 7.ane do about http://home.comcast.internet/~kmbtib/Fortran_stuff/elem_assign.f90 for instance?  If you lot use any compiler as your primary development compiler for a while you lot are going to come 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 not be the case.  How can y'all write a issues-gratis compiler to an inconsistent standard? -- write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, & six.0134700243160014d-154/),(/'10'/)); end
Wed, 02 Jan 2008 00:40:00 GMT
Paul Van Dels #23 / 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 7.1 in implementing the Fortran 95 >>standard. The few complaints I take seen well-nigh LF95 in this newsgroup >>business organisation 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 there in the current version.  What does LF95 7.1 > do about > http://home.comcast.net/~kmbtib/Fortran_stuff/elem_assign.f90 Dunno nigh the windows vii.ane, simply the unix 6.2c does the following: lnx:scratch : lf95 blah.f90 Encountered 0 errors, 0 warnings in file blah.f90. lnx:scratch : a.out original ten =  7 11 13 permuted x =  11 xiii 7 new x =  11 13 11 And v8.1 intel: lnx:scratch : ifort -static-libcxa blah.f90 lnx:scratch : a.out original ten =            7          eleven          13 permuted ten =           11          xiii           7 new x =           11          13          eleven g95 seems to get it correct though (at least I recall and then): lnx:scratch : g95 blah.f90 lnx:scratch : a.out original x =  7 xi 13 permuted x =  11 13 7 new 10 =  11 13 7 thank you, 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 it right though (at to the lowest degree I remember so): Yes, Andy wrote me a notation a while back to allow me know that he had fixed this issues.  It is so agreeable that both LF95 and ifort have the same mistake here.  Even surrounding the dexter of the assignment with parentheses doesn't assist these compilers out! -- write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, & 6.0134700243160014d-154/),(/'10'/)); cease
Wed, 02 Jan 2008 01:00:59 GMT
Steve Lione #25 / 25	fortran ninety compiler for linux On Fri, 15 Jul 2005 xi:00:59 -0600, "James Van Buskirk" Quote: >> g95 seems to get information technology right though (at to the lowest degree I remember so): >Yes, Andy wrote me a annotation a while back to permit me know that >he had fixed this bug.  It is and so amusing that both LF95 and >ifort have the same error hither.  Even surrounding the dexter >of the assignment with parentheses doesn't help these >compilers out! Now that information technology has been brought to our attention, we'll fix information technology too. Steve Lionel Software Products Division Intel Corporation Nashua, NH User communities for Intel Software Evolution Products http://softwareforums.intel.com/ Intel Fortran Support http://programmer.intel.com/software/products/back up/
Wed, 02 January 2008 03:31:32 GMT

Page 2 of two

[ 25 post ]

Go to page: [1] [ii]

Powered past phpBB® Forum Software

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

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

Share this post