public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55756] New: [4.8 regression] FAIL: gfortran.dg/same_type_as_1.f03  -O  (test for excess errors)
Date: Thu, 20 Dec 2012 14:38:00 -0000	[thread overview]
Message-ID: <bug-55756-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55756
           Summary: [4.8 regression] FAIL: gfortran.dg/same_type_as_1.f03
                    -O  (test for excess errors)
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: schwab@linux-m68k.org


spawn
/daten/aranym/gcc/gcc-20121220/Build/gcc/testsuite/gfortran/../../gfortran
-B/daten/aranym/gcc/gcc-20121220/Build/gcc/testsuite/gfortran/../../
-B/daten/aranym/gcc/gcc-20121220/Build/m68k-linux/./libgfortran/
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03
-fno-diagnostics-show-caret -O -pedantic-errors -S -o same_type_as_1.s

output is:
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03:21.24:

 print *, SAME_TYPE_AS (i,x1)   ! { dg-error "must be of a derived type" }
                        1
Error: 'a' argument of 'same_type_as' intrinsic at (1) cannot be of type
INTEGER(4)
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03:22.27:

 print *, SAME_TYPE_AS (x1,x2)  ! { dg-error "must be of an extensible type" }
                           1
Error: 'b' argument of 'same_type_as' intrinsic at (1) must be of an extensible
type
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03:24.27:

 print *, EXTENDS_TYPE_OF (i,x1)   ! { dg-error "must be of a derived type" }
                           1
Error: 'a' argument of 'extends_type_of' intrinsic at (1) cannot be of type
INTEGER(4)
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03:25.30:

 print *, EXTENDS_TYPE_OF (x1,x2)  ! { dg-error "must be of an extensible type"
                              1
Error: 'mold' argument of 'extends_type_of' intrinsic at (1) must be of an
extensible type

FAIL: gfortran.dg/same_type_as_1.f03  -O   (test for errors, line 21)
PASS: gfortran.dg/same_type_as_1.f03  -O   (test for errors, line 22)
FAIL: gfortran.dg/same_type_as_1.f03  -O   (test for errors, line 24)
PASS: gfortran.dg/same_type_as_1.f03  -O   (test for errors, line 25)
FAIL: gfortran.dg/same_type_as_1.f03  -O  (test for excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03:21:24:
Error: 'a' argument of 'same_type_as' intrinsic at (1) cannot be of type
INTEGER(4)
/daten/aranym/gcc/gcc-20121220/gcc/testsuite/gfortran.dg/same_type_as_1.f03:24:27:
Error: 'a' argument of 'extends_type_of' intrinsic at (1) cannot be of type
INTEGER(4)


             reply	other threads:[~2012-12-20 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 14:38 schwab@linux-m68k.org [this message]
2012-12-20 14:39 ` [Bug fortran/55756] " rguenth at gcc dot gnu.org
2012-12-20 15:29 ` burnus at gcc dot gnu.org
2012-12-20 18:07 ` [Bug testsuite/55756] " pault at gcc dot gnu.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=bug-55756-4@http.gcc.gnu.org/bugzilla/ \
    --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).