summaryrefslogtreecommitdiff
path: root/gcc/testsuite/gfortran.dg/impure_assignment_2.f90
diff options
context:
space:
mode:
authorupstream source tree <ports@midipix.org>2015-03-15 20:14:05 -0400
committerupstream source tree <ports@midipix.org>2015-03-15 20:14:05 -0400
commit554fd8c5195424bdbcabf5de30fdc183aba391bd (patch)
tree976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/gfortran.dg/impure_assignment_2.f90
downloadcbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2
cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository.
Diffstat (limited to 'gcc/testsuite/gfortran.dg/impure_assignment_2.f90')
-rw-r--r--gcc/testsuite/gfortran.dg/impure_assignment_2.f9070
1 files changed, 70 insertions, 0 deletions
diff --git a/gcc/testsuite/gfortran.dg/impure_assignment_2.f90 b/gcc/testsuite/gfortran.dg/impure_assignment_2.f90
new file mode 100644
index 000000000..6378ec8a4
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/impure_assignment_2.f90
@@ -0,0 +1,70 @@
+! { dg-do compile }
+! Tests the fix for PR20863 and PR20882, which were concerned with incorrect
+! application of constraints associated with "impure" variables in PURE
+! procedures.
+!
+! resolve.c (gfc_impure_variable) detects the following:
+! 12.6 Constraint: In a pure subprogram any variable which is in common or
+! accessed by host or use association, is a dummy argument to a pure function,
+! is a dummy argument with INTENT (IN) to a pure subroutine, or an object that
+! is storage associated with any such variable, shall not be used in the
+! following contexts: (clients of this function). */
+!
+! Contributed by Joost VandeVondele <jv244@cam.ac.uk>
+!
+MODULE pr20863
+ TYPE node_type
+ TYPE(node_type), POINTER :: next=>null()
+ END TYPE
+CONTAINS
+! Original bug - pointer assignments to "impure" derived type with
+! pointer component.
+ PURE FUNCTION give_next1(node)
+ TYPE(node_type), POINTER :: node
+ TYPE(node_type), POINTER :: give_next
+ give_next => node%next ! { dg-error "Bad target" }
+ node%next => give_next ! { dg-error "variable definition context" }
+ END FUNCTION
+! Comment #2
+ PURE integer FUNCTION give_next2(i)
+ TYPE node_type
+ sequence
+ TYPE(node_type), POINTER :: next
+ END TYPE
+ TYPE(node_type), POINTER :: node
+ TYPE(node_type), target :: t
+ integer, intent(in) :: i
+ node%next = t ! This is OK
+ give_next2 = i
+ END FUNCTION
+ PURE FUNCTION give_next3(node)
+ TYPE(node_type), intent(in) :: node
+ TYPE(node_type) :: give_next
+ give_next = node ! { dg-error "impure variable" }
+ END FUNCTION
+END MODULE pr20863
+
+MODULE pr20882
+ TYPE T1
+ INTEGER :: I
+ END TYPE T1
+ TYPE(T1), POINTER :: B
+CONTAINS
+ PURE FUNCTION TST(A) RESULT(RES)
+ TYPE(T1), INTENT(IN), TARGET :: A
+ TYPE(T1), POINTER :: RES
+ RES => A ! { dg-error "Bad target" }
+ RES => B ! { dg-error "Bad target" }
+ B => RES ! { dg-error "variable definition context" }
+ END FUNCTION
+ PURE FUNCTION TST2(A) RESULT(RES)
+ TYPE(T1), INTENT(IN), TARGET :: A
+ TYPE(T1), POINTER :: RES
+ allocate (RES)
+ RES = A
+ B = RES ! { dg-error "variable definition context" }
+ RES = B
+ END FUNCTION
+END MODULE pr20882
+! { dg-final { cleanup-modules "pr20863 pr20882" } }
+