[Bug fortran/20006] New: $ format extension accepted in error under -std=f95

[Bug fortran/20006] New: $ format extension accepted in error under -std=f95

[tow21 at cam dot ac dot uk]

Using the $ character in a write format is a commonly-implemented extension to 
imply non-advancing output; it is, however, not part of any Fortran standard 
(f90 and later standards offer an alternative method to achieve the same aim). 
 
However, gfortran currently accepts it without complaint. 
 
parabrisas:~/test% cat testRead.f  
 
      program testRead 
      implicit none 
      print '(a,$)','hello world' 
      print * 
      end 
parabrisas:~/test% gfortran -std=f95 testRead.f  
parabrisas:~/test%

-- 
           Summary: $ format extension accepted in error under -std=f95
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tow21 at cam dot ac dot uk
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension accepted in error under -std=f95

[jv244 at cam dot ac dot uk]

------- Additional Comments From jv244 at cam dot ac dot uk  2005-02-16 12:32 -------
> However, gfortran currently accepts it without complaint. 

However, in general, this can only be found at runtime (also with NAG f95):

program testRead

implicit none
character(len=19) fmt
character(1) resp

! assume this is well hidden in a different subroutine
fmt='('' hit return: '',$)' 

write (*,fmt=fmt)
read (*,'(a)') resp

write (*,'('' well done.'')')
end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension accepted in error under -std=f95

[tow21 at cam dot ac dot uk]

------- Additional Comments From tow21 at cam dot ac dot uk  2005-02-16 15:44 -------
(In reply to comment #1) 
> > However, gfortran currently accepts it without complaint.  
>  
> However, in general, this can only be found at runtime (also with NAG f95): 
 
[snip example] 
 
Of course, you're right. Maybe this bug should be reported against libfortran 
as well? Don't know - I shall leave it to whoever confirms it. 
 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension accepted in error under -std=f95

[coudert at clipper dot ens dot fr]

------- Additional Comments From coudert at clipper dot ens dot fr  2005-02-22 10:39 -------
I can't reproduce the behaviour reported. All I see is that gfortran is ignoring
the $ character:

$ cat a.f90 
      program testRead 
      implicit none 
      print '(a,$)','hello world' 
      print *
      end 
$ gfortran -std=f95 a.f90 && ./a.out
hello world

$ ifort a.f90 && ./a.out            
hello world 
$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/tmp/gfortran-20050222/irun
--enable-languages=c,f95
Thread model: posix
gcc version 4.0.0 20050222 (experimental)

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension doesn't work

[fxcoudert at gcc dot gnu dot org]

------- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-04-12 13:04 -------
OK. I have a patch to make $ work, I'll add a warning when this is possible at
compile-time (I don't think we want to have a warning at runtime, especially
since there is general agreement on this extension).

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |fxcoudert at gcc dot gnu dot
                   |dot org                     |org
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-04-12 13:04:30
               date|                            |
            Summary|$ format extension accepted |$ format extension doesn't
                   |in error under -std=f95     |work


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension doesn't work

[tow21 at cam dot ac dot uk]

------- Additional Comments From tow21 at cam dot ac dot uk  2005-04-12 13:18 -------
(In reply to comment #4)  
> OK. I have a patch to make $ work, I'll add a warning when this is possible  
at  
> compile-time (I don't think we want to have a warning at runtime, especially  
> since there is general agreement on this extension).  
  
As an extension, that's fine. But if I've compiled with -pedantic -std=f95,  
then I'd expect an error where possible at compile-time, and a fatal IO error 
at runtime. 
  

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension doesn't work

[fxcoudert at gcc dot gnu dot org]

------- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-04-12 14:31 -------
Fatal I/O error for an extension that everybody agrees on? Wahoo! I'm not sure
any compiler does that...

In my mind, being pedantic (that is, issuing fatal errors) makes sense at
compile-time, but it is very harsh to do so at runtime. I can imagine how, as a
researcher, I would compile with -pedantic, be glad that no error turn out, then
run a one-week simulation code and see it issue a fatal error instead of
printing the results at the end...

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug fortran/20006] $ format extension doesn't work

[tow21 at cam dot ac dot uk]

------- Additional Comments From tow21 at cam dot ac dot uk  2005-04-12 14:46 -------
(In reply to comment #6) 
> Fatal I/O error for an extension that everybody agrees on? Wahoo! I'm not > 
> sure any compiler does that... 
 
But "everyone" doesn't agree on it. Otherwise it would be standard, not an 
extension,. If I compile with -pedantic -std=f95, then I'm saying I don't want 
any extensions, regardless of how many people agree on them. 
 
> In my mind, being pedantic (that is, issuing fatal errors) makes sense at 
> compile-time, but it is very harsh to do so at runtime. I can imagine how,  
> as a researcher, I would compile with -pedantic, be glad that no error turn 
> out, then run a one-week simulation code and see it issue a fatal error  
> instead of printing the results at the end... 
 
Then I think you're putting too much trust in -pedantic. This is why, for 
example, even if my codes compile with -pedantic, I'll run them thoroughly 
with -C. You can't catch every possible error at compile time. 
 
I would be equally annoyed if having run everything through with full 
-pedantic and error-checking on gfortran, I assumed that my code was fully 
standard-conforming, moved my code across to NAG fortran, and it crashed with 
 
Invalid edit descriptor beginning with '$' 
Program terminated by fatal I/O error 
zsh: 27142 abort (core dumped)  ./a.out 
 
which it would, because that's what it does now.  
 
Not, of course, that we can catch every standard violation, but I would expect 
that this be caught. 
 
 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[fxcoudert at gcc dot gnu dot org]

------- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-05-22 21:32 -------
OK, let's try it again. The facts are the following:
  1. there is no mechanism in gfortran to issue warnings at runtime when those
depend on compilation flags
  2. the meaning of $ as an edit descriptor is not ambiguous

I will submit a patch to enable $ as an edit descriptor, issue a warning if this
descriptor is found at compile time (for example, in a format statement, or in a
constant format string). And we'll keep this PR open to remember that when point
1 above (no strict conformance warnings in library) is fixed, I'll add the check
needed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|fortran                     |libfortran


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-05-29 12:23 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	fxcoudert@gcc.gnu.org	2005-05-29 12:22:50

Modified files:
	gcc/fortran    : ChangeLog io.c 
	libgfortran    : ChangeLog 
	libgfortran/io : format.c transfer.c 

Log message:
	PR libfortran/20006
	* io.c (format_item_1): Add check and extension warning for
	$ edit descriptor.
	* io/format.c (parse_format_list): Set repeat count of $ format
	node to 1.
	* io/transfer.c (read_sf): Add g.seen_dollar to the test
	concerning advancing I/O.
	(data_transfer_init): Likewise.
	(finalize_transfer): Likewise.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.437&r2=1.438
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/io.c.diff?cvsroot=gcc&r1=1.22&r2=1.23
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.230&r2=1.231
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/format.c.diff?cvsroot=gcc&r1=1.12&r2=1.13
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&r1=1.41&r2=1.42


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-05-29 12:23 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-4_0-branch
Changes by:	fxcoudert@gcc.gnu.org	2005-05-29 12:22:54

Modified files:
	gcc/fortran    : ChangeLog io.c 
	libgfortran    : ChangeLog 
	libgfortran/io : format.c transfer.c 

Log message:
	PR libfortran/20006
	* io.c (format_item_1): Add check and extension warning for
	$ edit descriptor.
	* io/format.c (parse_format_list): Set repeat count of $ format
	node to 1.
	* io/transfer.c (read_sf): Add g.seen_dollar to the test
	concerning advancing I/O.
	(data_transfer_init): Likewise.
	(finalize_transfer): Likewise.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.335.2.56&r2=1.335.2.57
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/io.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.19.10.2&r2=1.19.10.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.44&r2=1.163.2.45
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/format.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.9.12.1&r2=1.9.12.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.32.2.3&r2=1.32.2.4



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-05-29 12:23 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	fxcoudert@gcc.gnu.org	2005-05-29 12:22:50

Modified files:
	gcc/fortran    : ChangeLog io.c 
	libgfortran    : ChangeLog 
	libgfortran/io : format.c transfer.c 

Log message:
	PR libfortran/20006
	* io.c (format_item_1): Add check and extension warning for
	$ edit descriptor.
	* io/format.c (parse_format_list): Set repeat count of $ format
	node to 1.
	* io/transfer.c (read_sf): Add g.seen_dollar to the test
	concerning advancing I/O.
	(data_transfer_init): Likewise.
	(finalize_transfer): Likewise.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.437&r2=1.438
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/io.c.diff?cvsroot=gcc&r1=1.22&r2=1.23
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.230&r2=1.231
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/format.c.diff?cvsroot=gcc&r1=1.12&r2=1.13
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&r1=1.41&r2=1.42


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-05-29 12:23 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-4_0-branch
Changes by:	fxcoudert@gcc.gnu.org	2005-05-29 12:22:54

Modified files:
	gcc/fortran    : ChangeLog io.c 
	libgfortran    : ChangeLog 
	libgfortran/io : format.c transfer.c 

Log message:
	PR libfortran/20006
	* io.c (format_item_1): Add check and extension warning for
	$ edit descriptor.
	* io/format.c (parse_format_list): Set repeat count of $ format
	node to 1.
	* io/transfer.c (read_sf): Add g.seen_dollar to the test
	concerning advancing I/O.
	(data_transfer_init): Likewise.
	(finalize_transfer): Likewise.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.335.2.56&r2=1.335.2.57
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/io.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.19.10.2&r2=1.19.10.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.44&r2=1.163.2.45
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/format.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.9.12.1&r2=1.9.12.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.32.2.3&r2=1.32.2.4



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[fxcoudert at gcc dot gnu dot org]

------- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-08-03 18:55 -------
Patch proposed to add the general runtime warning mechanism to libgfortran,
which solves this PR.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://gcc.gnu.org/ml/gcc-
                   |                            |patches/2005-
                   |                            |08/msg00205.html
           Keywords|                            |patch


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-08-11 13:50 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	fxcoudert@gcc.gnu.org	2005-08-11 13:50:13

Modified files:
	gcc/fortran    : ChangeLog gfortran.h trans-decl.c trans.c 
	                 trans.h 
	libgfortran    : ChangeLog Makefile.am Makefile.in libgfortran.h 
	libgfortran/io : format.c 
	libgfortran/runtime: error.c main.c 
Added files:
	gcc/testsuite/gfortran.dg: runtime_warning_1.f90 
	libgfortran/runtime: compile_options.c 

Log message:
	PR libfortran/20006
	* gfortran.h: Add is_main_program member to symbol_attribute.
	* trans-decl: Add a gfor_fndecl_set_std tree.
	(gfc_build_builtin_function_decls): Create it.
	(gfc_generate_function_code): Add this call at the beginning of
	the main program.
	* trans.c (gfc_generate_code): Move main_program and attr.
	* trans.h: Add declaration for gfor_fndecl_set_std.
	
	* Makefile.am: Add file runtime/compile_options.c.
	* Makefile.in: Regenerate.
	* libgfortran.h: Create structure compile_options_t. Define the
	compile_options variable and GFC_STD_ macros.
	* runtime/compile_options.c: New file.
	* runtime/error.c (notify_std): New function.
	* runtime/main.c (init): Call init_compile_options during
	initialization.
	* io/format.c: Use the new notify_std function for the $
	descriptor extension.
	
	* gfortran.dg/runtime_warning_1.f90: New test.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.519&r2=1.520
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/gfortran.h.diff?cvsroot=gcc&r1=1.79&r2=1.80
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-decl.c.diff?cvsroot=gcc&r1=1.65&r2=1.66
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans.c.diff?cvsroot=gcc&r1=1.27&r2=1.28
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans.h.diff?cvsroot=gcc&r1=1.31&r2=1.32
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/runtime_warning_1.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.282&r2=1.283
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/Makefile.am.diff?cvsroot=gcc&r1=1.40&r2=1.41
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/Makefile.in.diff?cvsroot=gcc&r1=1.42&r2=1.43
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/libgfortran.h.diff?cvsroot=gcc&r1=1.28&r2=1.29
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/format.c.diff?cvsroot=gcc&r1=1.13&r2=1.14
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/compile_options.c.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/error.c.diff?cvsroot=gcc&r1=1.11&r2=1.12
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/main.c.diff?cvsroot=gcc&r1=1.7&r2=1.8



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[fxcoudert at gcc dot gnu dot org]

------- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-08-11 13:52 -------
This bug is fixed: we now have a framework for runtime warnings about standard
conformance, and we use it in this case.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.0.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-08-11 13:53 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-4_0-branch
Changes by:	fxcoudert@gcc.gnu.org	2005-08-11 13:53:22

Modified files:
	gcc/fortran    : ChangeLog gfortran.h trans-decl.c trans.c 
	                 trans.h 
	gcc/testsuite  : ChangeLog 
	libgfortran    : ChangeLog Makefile.am Makefile.in aclocal.m4 
	                 libgfortran.h 
	libgfortran/io : format.c 
	libgfortran/runtime: error.c main.c 

Log message:
	PR libfortran/20006
	* gfortran.h: Add is_main_program member to symbol_attribute.
	* trans-decl: Add a gfor_fndecl_set_std tree.
	(gfc_build_builtin_function_decls): Create it.
	(gfc_generate_function_code): Add this call at the beginning of
	the main program.
	* trans.c (gfc_generate_code): Move main_program and attr.
	* trans.h: Add declaration for gfor_fndecl_set_std.
	* Makefile.am: Add file runtime/compile_options.c.
	* Makefile.in: Regenerate.
	* aclocal.m4: Regenerate.
	* libgfortran.h: Create structure compile_options_t. Define the
	compile_options variable and GFC_STD_ macros.
	* runtime/compile_options.c: New file.
	* runtime/error.c (notify_std): New function.
	* runtime/main.c (init): Call init_compile_options during
	initialization.
	* io/format.c: Use the new notify_std function for the $
	descriptor extension.
	* gfortran.dg/runtime_warning_1.f90: New test.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.335.2.104&r2=1.335.2.105
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/gfortran.h.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.58.2.13&r2=1.58.2.14
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-decl.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.54.2.4&r2=1.54.2.5
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.21.10.1&r2=1.21.10.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans.h.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.23.2.4&r2=1.23.2.5
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.5084.2.329&r2=1.5084.2.330
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.76&r2=1.163.2.77
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/Makefile.am.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.29.10.7&r2=1.29.10.8
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/Makefile.in.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.30.10.6&r2=1.30.10.7
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/aclocal.m4.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.6.12.3&r2=1.6.12.4
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/libgfortran.h.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.23.8.3&r2=1.23.8.4
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/format.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.9.12.3&r2=1.9.12.4
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/error.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.9&r2=1.9.12.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/main.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.6&r2=1.6.12.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006

[Bug libfortran/20006] $ format extension doesn't work

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-08-12 05:59 -------
Subject: Bug 20006

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-4_0-branch
Changes by:	aj@gcc.gnu.org	2005-08-12 05:58:57

Added files:
	libgfortran/runtime: compile_options.c 

Log message:
	Add missing file from commit for PR libfortran/20006.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/compile_options.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.2.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006