[Bug fortran/39532] fortran 95 parsing trouble

2009-03-23 Thread kargl at gcc dot gnu dot org
--- Comment #4 from kargl at gcc dot gnu dot org 2009-03-23 21:30 --- Confirmed with Patrick that the source code is assumed to be fixed-form by gfortran and the code contains lines longer than 72 characters. Patrick confirmed that the option -ffixed-line-length-none allows the code to

[Bug fortran/39532] fortran 95 parsing trouble

2009-03-23 Thread kargl at gcc dot gnu dot org
--- Comment #3 from kargl at gcc dot gnu dot org 2009-03-23 20:25 --- (In reply to comment #2) > I just tried > > ifort -warn stderrors -std95 modules.f > > which didn't complain. It seems gfortran is unhappy about the parentheses > in that declaration. I included the parts before, so

[Bug fortran/39532] fortran 95 parsing trouble

2009-03-23 Thread prlw1 at cam dot ac dot uk
--- Comment #2 from prlw1 at cam dot ac dot uk 2009-03-23 20:23 --- I just tried ifort -warn stderrors -std95 modules.f which didn't complain. It seems gfortran is unhappy about the parentheses in that declaration. I included the parts before, so you can see that nREBOspecies is define

[Bug fortran/39532] fortran 95 parsing trouble

2009-03-23 Thread kargl at gcc dot gnu dot org
--- Comment #1 from kargl at gcc dot gnu dot org 2009-03-23 20:01 --- Please attach the offending code. Also, ifort has an option for fairly strict conformance to the Fortran 95 standard. Does the code compile with this option. -- kargl at gcc dot gnu dot org changed: W