http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46327
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2010-11-06 06:49:55 UTC --- On Fri, Nov 05, 2010 at 11:19:57PM -0700, Steve Kargl wrote: > On Sat, Nov 06, 2010 at 05:01:45AM +0000, jan.kratochvil at redhat dot com > wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46327 > > > > --- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> > > 2010-11-06 05:01:35 UTC --- > > (In reply to comment #1) > > > Hopefully, this will never be supported in gfortran. > > > > The problem is users continue to use iFort and I have to continue > > supporting it > > in GDB as they sources work fine in iFort. It is fine if an explicit > > gfortran > > compilation option is required. > > > > Their source may work fine with ifort, but it is > not standard conforming Fortran. If they need > to debug their code, then they should use Intel's > debugger. Their code will not compile with > gfortran, so trying to debug gfortran compiled > Fortran code should not be an issue with gdb. Having thought about this for a few more minutes, I can't see the issue. The compile pipelines are Fortran code --> ifort --> gdb Fortran code --> gfortran --> gdb I simply fail to see why gfortran needs to support the dot syntax. This seems to be a purely gdb issue. Do you want to support ifort syntax or not?
