public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/22302] New: gfortran.dg/io_invalid_1.f90 has an erroneous test pattern
Date: Tue, 05 Jul 2005 02:00:00 -0000	[thread overview]
Message-ID: <20050705020049.22302.hp@gcc.gnu.org> (raw)

The new test gfortran.dg/io_invalid_1.f90 fails for cris-axis-linux-gnu,
but I expect it to fail everywhere:
FAIL: gfortran.dg/io_invalid_1.f90  -O   (test for errors, line 3)
FAIL: gfortran.dg/io_invalid_1.f90  -O  (test for excess errors)

gfortran.log says:
/home/hp/combined/combined/gcc/testsuite/gfortran.dg/io_invalid_1.f90   -O  
-pedantic-errors -S    -o io_invalid_1.s    (timeout = 300)
 In file
/home/hp/combined/combined/gcc/testsuite/gfortran.dg/io_invalid_1.f90:3^M
^M
WRITE(UNIT=6,END=999) 0 ! { dg-error "END tag .* is not compatible with
output"^M
                   1^M
Error: END tag at (1) not allowed in output statement^M

Apparently the expected error message is something other than what is emitted.
I don't know which is right or if the bug is elsewhere.

Committer of test-case CC:ed.

-- 
           Summary: gfortran.dg/io_invalid_1.f90 has an erroneous test
                    pattern
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
                CC: fxcoudert at gcc dot gnu dot org,gcc-bugs at gcc dot gnu
                    dot org
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: cris-axis-linux-gnu


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


             reply	other threads:[~2005-07-05  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05  2:00 hp at gcc dot gnu dot org [this message]
2005-07-05  2:05 ` [Bug testsuite/22302] " pinskia at gcc dot gnu dot org
2005-07-05  2:08 ` 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=20050705020049.22302.hp@gcc.gnu.org \
    --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).