From 1bc5aee63eb72b341f506ad058502cd0361f0d10 Mon Sep 17 00:00:00 2001 From: Ben Cheng Date: Tue, 25 Mar 2014 22:37:19 -0700 Subject: Initial checkin of GCC 4.9.0 from trunk (r208799). Change-Id: I48a3c08bb98542aa215912a75f03c0890e497dba --- .../testsuite/gfortran.dg/typebound_proc_13.f03 | 46 ++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 gcc-4.9/gcc/testsuite/gfortran.dg/typebound_proc_13.f03 (limited to 'gcc-4.9/gcc/testsuite/gfortran.dg/typebound_proc_13.f03') diff --git a/gcc-4.9/gcc/testsuite/gfortran.dg/typebound_proc_13.f03 b/gcc-4.9/gcc/testsuite/gfortran.dg/typebound_proc_13.f03 new file mode 100644 index 000000000..98caac692 --- /dev/null +++ b/gcc-4.9/gcc/testsuite/gfortran.dg/typebound_proc_13.f03 @@ -0,0 +1,46 @@ +! { dg-do compile } + +! PR fortran/41177 +! Test for additional errors with type-bound procedure bindings. +! Namely that non-scalar base objects are rejected for TBP calls which are +! NOPASS, and that passed-object dummy arguments must be scalar, non-POINTER +! and non-ALLOCATABLE. + +MODULE m + IMPLICIT NONE + + TYPE t + CONTAINS + PROCEDURE, NOPASS :: myproc + END TYPE t + + TYPE t2 + CONTAINS + PROCEDURE, PASS :: nonscalar ! { dg-error "must be scalar" } + PROCEDURE, PASS :: is_pointer ! { dg-error "must not be POINTER" } + PROCEDURE, PASS :: is_allocatable ! { dg-error "must not be ALLOCATABLE" } + END TYPE t2 + +CONTAINS + + SUBROUTINE myproc () + END SUBROUTINE myproc + + SUBROUTINE nonscalar (me) + CLASS(t2), INTENT(IN) :: me(:) + END SUBROUTINE nonscalar + + SUBROUTINE is_pointer (me) + CLASS(t2), POINTER, INTENT(IN) :: me + END SUBROUTINE is_pointer + + SUBROUTINE is_allocatable (me) + CLASS(t2), ALLOCATABLE, INTENT(IN) :: me + END SUBROUTINE is_allocatable + + SUBROUTINE test () + TYPE(t) :: arr(2) + CALL arr%myproc () ! { dg-error "must be scalar" } + END SUBROUTINE test + +END MODULE m -- cgit v1.2.3