From: Tobias Burnus <burnus@net-b.de>
To: "'fortran@gcc.gnu.org'" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [patch, fortran] Support .F03 and .f03 file extensions
Date: Sat, 06 Jan 2007 10:45:00 -0000 [thread overview]
Message-ID: <459F7DC0.9010409@net-b.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
:ADDPATCH fortran:
Support the .f03 and .F03 file extensions.
Ok for the trunk?
Bootstrapped, tested and regression tested on x86_64-unknown-linux-gnu
Tobias
2007-01-06 Tobias Burnus <burnus@net-b.de>
* lang-specs.h: Add support for .f03 and .F03 extensions.
* gfortran.texi: Document .f03 extension.
* options.c (form_from_filename): Recognize .f03.
[-- Attachment #2: f03.diff --]
[-- Type: text/x-patch, Size: 2195 bytes --]
Index: gcc/fortran/gfortran.texi
===================================================================
--- gcc/fortran/gfortran.texi (Revision 120520)
+++ gcc/fortran/gfortran.texi (Arbeitskopie)
@@ -367,8 +367,8 @@
Fortran) for each file in the source code, and then calls the assembler
and linker as appropriate to produce the compiled output. In a copy of
GCC which has been compiled with Fortran language support enabled,
-@command{gcc} will recognize files with @file{.f}, @file{.f90}, and
-@file{.f95} extensions as Fortran source code, and compile it
+@command{gcc} will recognize files with @file{.f}, @file{.f90}, @file{.f95},
+and @file{.f03} extensions as Fortran source code, and compile it
accordingly. A @command{gfortran} driver program is also provided,
which is identical to @command{gcc} except that it automatically links
the Fortran runtime libraries into the compiled program.
Index: gcc/fortran/options.c
===================================================================
--- gcc/fortran/options.c (Revision 120520)
+++ gcc/fortran/options.c (Arbeitskopie)
@@ -137,6 +138,9 @@
".f95", FORM_FREE}
,
{
+ ".f03", FORM_FREE}
+ ,
+ {
".f", FORM_FIXED}
,
{
Index: gcc/fortran/lang-specs.h
===================================================================
--- gcc/fortran/lang-specs.h (Revision 120520)
+++ gcc/fortran/lang-specs.h (Arbeitskopie)
@@ -18,6 +18,7 @@
-fpreprocessed %{!nostdinc:-fintrinsic-modules-path finclude%s} %{!fsyntax-only:%(invoke_as)}}}}", 0, 0, 0},
{".F90", "@f95-cpp-input", 0, 0, 0},
{".F95", "@f95-cpp-input", 0, 0, 0},
+{".F03", "@f95-cpp-input", 0, 0, 0},
{"@f95-cpp-input",
"cc1 -E -lang-fortran -traditional-cpp -D_LANGUAGE_FORTRAN %(cpp_options) \
%{E|M|MM:%(cpp_debug_options)}\
@@ -26,6 +27,7 @@
-fpreprocessed %{!nostdinc:-fintrinsic-modules-path finclude%s} %{!fsyntax-only:%(invoke_as)}}}}", 0, 0, 0},
{".f90", "@f95", 0, 0, 0},
{".f95", "@f95", 0, 0, 0},
+{".f03", "@f95", 0, 0, 0},
{"@f95", "%{!E:f951 %i %(cc1_options) %{J*} %{I*}\
%{!nostdinc:-fintrinsic-modules-path finclude%s} %{!fsyntax-only:%(invoke_as)}}", 0, 0, 0},
{".f", "@f77", 0, 0, 0},
next reply other threads:[~2007-01-06 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 10:45 Tobias Burnus [this message]
2007-01-17 18:15 ` Tobias Burnus
2007-01-17 18:37 ` FX Coudert
2007-01-17 18:42 ` Tobias Burnus
2007-01-17 18:59 ` FX Coudert
2007-01-17 19:34 ` Tobias Burnus
2007-01-17 21:10 ` Tobias Burnus
2007-01-22 21:36 ` Tobias Burnus
2007-01-22 21:38 ` Andrew Pinski
2007-01-22 21:55 ` Brooks Moses
2007-01-25 23:06 ` FX Coudert
2007-01-26 8:11 ` Tobias Burnus
2007-01-26 8:23 ` Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=459F7DC0.9010409@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).