Providing an argument that has not the TARGET attribute to a procedure with a dummy argument that has the TARGET attribute

by

You are correct that you have invalid code. It isn’t, though, for the reason you say.

Within a procedure, it is legal for a dummy argument to have the target attribute even though the associated actual argument hasn’t. Essentially, we are allowed to have pointers targeting the entity within the procedure as long as the lifetime of this pointing doesn’t exceed the lifetime of the procedure.

In the case of this question, the dummy argument tab is allowed to have the target attribute even though the associated actual argument A hasn’t. Even the pointer assignment statement ptr_tab => tab within the procedure is legal.

What is important, however, is that outside the procedure, where the actual argument hasn’t the target attribute, we can’t affect that entity through a pointer. The Fortran standard ensures this doesn’t happen in the following way (Fortran 2008 C.9.4, see also 12.5.2.4; similar exists in Fortran 2018):

If a nonpointer dummy argument has the TARGET attribute and the corresponding actual argument does not, any pointers that become associated with the dummy argument, and therefore with the actual argument, during
execution of the procedure, become undefined when execution of the procedure completes.

That is, in the case of the question, on completion of pointerize ptr_A is no longer of defined association status. Deferencing this pointer in the main program’s print statement is not allowed.

For interest, compiling the example code with nagfor results in the run-time diagnostic

Runtime Error: aaa.f90, line 9: Reference to dangling pointer PTR_A
Target was RETURNed from procedure POINTERIZATION:POINTERIZE
Program terminated by fatal error
Abort (core dumped)

But equally, just because the pointer association is undefined, this doesn’t mean that you can’t get the results you expect. Such checking is a nice thing from a compiler but it isn’t required that it should fail.

More Related Contents:

  1. Fortran running error
  2. Fortran: integer*4 vs integer(4) vs integer(kind=4)
  3. Why Segmentation fault is happening in this openmp code?
  4. Unexpected “padding” in a Fortran unformatted file
  5. What is an undefined reference/unresolved external symbol error and how do I fix it in Fortran?
  6. Is There a Better Double-Precision Assignment in Fortran 90?
  7. changing array dimensions in fortran
  8. Why should I use interfaces?
  9. Sending 2D arrays in Fortran with MPI_Gather
  10. Fortran OpenMP program shows no speedup of CPU_TIME()
  11. Where to put `implicit none` in Fortran
  12. Function has no implicit type
  13. Print to standard output from a function defined in an Fortran module
  14. Why is this a function declared inside the module and then used somewhere else in the same module not seen by the linker?
  15. Does Fortran have undefined behavior?
  16. ‘*’ and ‘/’ not recognized on input by a read statement
  17. Reading data file in Fortran with known number of lines but unknown number of entries in each line
  18. What does “real*8” mean?
  19. What is the purpose of result variables in Fortran?
  20. Function in fortran, passing array in, receiving array out
  21. Fortran OpenMP with subroutines and functions
  22. Difference between intent(out) and intent(inout)
  23. Error: Nonnegative width required in format string at (1)
  24. Fortran intent(inout) versus omitting intent
  25. Fortran array cannot be returned in function: not a DUMMY variable
  26. Is Fortran unable to do the addition between 865398.78 and -865398.78? Why the answer is -0.03?
  27. Passing size as argument VS assuming shape in Fortran procedures
  28. Allocatable array valued function. gfortran vs ifort
  29. Fortran SAVE statement
  30. MPI_Gather gives seg fault in the most basic code

Leave a Comment