The ratfor support broke when we dropped the old f77 front end.
aretha$ touch tmp.r
aretha$ ./xgcc -B./ tmp.r
xgcc: tmp.r: Ratfor compiler not installed on this system
aretha$
This is the default message we get when a language hasn't been configured in,
but I did configure in the fortran compiler and hence something more
interesting should have happened.
An older compiler (gcc 3.3.3) gives me
aretha$ gcc tmp.r
gcc: installation problem, cannot exec `ratfor': No such file or directory
aretha$
which would have worked if I had the ratfor preprocessor installed.
It isn't clear to me if we should be dropping the ratfor support, or if we
should be fixing it. Hence this PR. A web search shows that the language is
still alive, but I can't recall the last time someone mentioned it on a gcc
list.
If we want to fix it, then we need to add a @ratfor spec to the
fortran/lang-specs.h file. Perhaps just one copied from the old f77 front end
would do.
If we want to remove it, then we need to delete the .r filename docs from
doc/invoke.texi. We need to delete ratfor from the -x language list. And we
need to delete the default .r support in the gcc.c file.
--
Summary: whither ratfor?
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wilson at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24357
