[Bug fortran/79933] gfortran no longer able to compile dolfyn benchmark

2017-11-04 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 --- Comment #6 from Steve Kargl --- On Sat, Nov 04, 2017 at 09:18:22PM +, tulipawn at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 > > --- Comment #5 from PeteVine --- > You're right, sorry for the confusion. It

[Bug fortran/79933] gfortran no longer able to compile dolfyn benchmark

2017-11-04 Thread tulipawn at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 --- Comment #5 from PeteVine --- You're right, sorry for the confusion. It seems I skimmed over the wall of errors too quickly while the last one came from a different source file. According to my own results in bug #77730, I was somehow able to

[Bug fortran/79933] gfortran no longer able to compile dolfyn benchmark

2017-11-04 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- C

[Bug fortran/79933] gfortran no longer able to compile dolfyn benchmark

2017-11-04 Thread tulipawn at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 --- Comment #3 from PeteVine --- In gcc 8, -std=f2003 is required to overcome the issue but there's another failure later on: gfortran -c -O2 -std=f2003solverinterface.f90 solverinterface.f90:108:9: real*4 fpar(16) ! hint by Shibo

[Bug fortran/79933] gfortran no longer able to compile dolfyn benchmark

2017-03-06 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 Jerry DeLisle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/79933] gfortran no longer able to compile dolfyn benchmark

2017-03-06 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79933 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org --- Comment