public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/13257] New: [gfortran] Error instead of warning for missing comma in format string
Date: Mon, 01 Dec 2003 05:18:00 -0000	[thread overview]
Message-ID: <20031201051818.13257.dann@godzilla.ics.uci.edu> (raw)

With: gcc version 3.5-tree-ssa 20031130 (merged 20031123)

test.f90
      subroutine mysub
      dimension ibar(5)
      write (3,1001) ( ibar(m), m = 1, 5 )

 1001 format (/5x,' ',i4' '/ )
      return
      end

gfortran -c test.f90 -ffixed-form                                              
                                               In file test.f90:5

 1001 format (/5x,' ',i4' '/ )
                           1
Error: Missing comma in format string at (1)
 In file test.f90:3

      write (3,1001) ( ibar(m), m = 1, 5 )
                  1
Error: FORMAT label 1001 at (1) not defined

g77 gives a warning, but still compiles the code.

Intel's compiler compiles the above code.

Code like this appears in SPEC95

-- 
           Summary: [gfortran] Error instead of warning for missing comma in
                    format string
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dann at godzilla dot ics dot uci dot edu
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2003-12-01  5:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  5:18 dann at godzilla dot ics dot uci dot edu [this message]
2003-12-01  6:02 ` [Bug fortran/13257] " pinskia at gcc dot gnu dot org
2003-12-02 15:43 ` pinskia at gcc dot gnu dot org
2004-04-26  4:17 ` pinskia at gcc dot gnu dot org
2004-05-18 13:11 ` pinskia at gcc dot gnu dot org
2004-05-26 18:31 ` pinskia at gcc dot gnu dot org
2005-01-06 14:40 ` [Bug fortran/13257] " tobi at gcc dot gnu dot org
2005-01-08 20:39 ` pinskia at gcc dot gnu dot org
2005-04-08 14:27 ` pinskia at gcc dot gnu dot org
2005-04-08 17:08 ` pinskia at gcc dot gnu dot org
2005-04-09 18:44 ` cvs-commit at gcc dot gnu dot org
2005-04-09 18:46 ` [Bug fortran/13257] [4.0 only] " pinskia at gcc dot gnu dot org
2005-06-06 10:45 ` giovannibajo at libero dot it
2005-07-01 22:16 ` pinskia at gcc dot gnu dot org
2005-07-16 20:47 ` cvs-commit at gcc dot gnu dot org
2005-07-16 20:47 ` pinskia at gcc dot gnu dot org

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=20031201051818.13257.dann@godzilla.ics.uci.edu \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).