Intel® Fortran Compiler 17.0 Developer Guide and Reference
Use the [Q]dyncom option to dynamically allocate common blocks at run time.
This option designates a common block to be dynamic. The space for its data is allocated at run time rather than at compile time. On entry to each routine containing a declaration of the dynamic common block, a check is performed to see whether space for the common block has been allocated. If the dynamic common block is not yet allocated, space is allocated at that time.
The following command-line example specifies the dynamic common option with the names of the common blocks to be allocated dynamically at run time:
ifort -dyncom "blk1,blk2,blk3" test.f ! Linux and OS X
ifort /Qdyncom"BLK1,BLK2,BLK3" test.f ! Windowswhere BLK1, BLK2, and BLK3 are the names of the common blocks to be made dynamic.
The following are some limitations that you should be aware of when using the [Q]dyncom option:
An entity in a dynamic common cannot be initialized in a DATA statement.
Only named common blocks can be designated as dynamic COMMON.
An entity in a dynamic common block must not be used in an EQUIVALENCE expression with an entity in a static common block or a DATA-initialized variable.
A main reason for using dynamic common blocks is to enable you to control the common block allocation by supplying your own allocation routine. To use your own allocation routine, you should link it ahead of the Fortran run-time library.
The C function prototype is:
void _FTN_ALLOC(void **mem, int *size, char *name);
where
mem is the location of the base pointer of the common block that must be set by the routine to point to the block of memory allocated.
size is the integer number of bytes of memory that the compiler has determined are necessary to allocate for the common block as it was declared in the program.
You can ignore this value and use whatever value is necessary for your purpose. You must return the size in bytes of the space you allocate. The library routine that calls the default or Fortran run-time function ensures that all other occurrences of this common block fit in the space you allocated. You can return the size in bytes of the space you allocate by modifying size.
name is the name of the common block being dynamically allocated.
The equivalent Fortran INTERFACE specification is:
interface
subroutine my_ftn_alloc (mem, size, name) bind (C, name="_FTN_ALLOC")
use, intrinsic :: ISO_C_BINDING
implicit none
type(C_PTR), intent(OUT) :: mem
integer(C_INT), intent(INOUT) :: size
character, dimension(*), intent(IN) :: name
end subroutine my_ftn_alloc
end interface
You can also use the Fortran run-time function FOR__SET_FTN_ALLOC to specify your own allocation routine. This method is especially helpful when you are using shared libraries. If you choose this method, it overrides the default routine _FTN_ALLOC.
For offload applications, routines FOR__SET_FTN_ALLOC and _FTN_ALLOC will work on native Intel® Many Integrated Core Architecture (Intel® MIC Architecture).
However, they will not work across the boundary between a host CPU and an Intel® MIC Architecture coprocessor. For example, if you use FOR__SET_FTN_ALLOC in the host-side code, it will work on COMMON allocations in other host-side code. The same is true if both are on the coprocessor side.
But if you change the allocation routine on the host, it won't be changed on the coprocessor and vice versa.
The run-time library routine, f90_dyncom, performs memory allocation. The compiler calls this routine at the beginning of each routine in a program that contains a dynamic common block. In turn, this library routine calls _FTN_ALLOC to allocate memory. By default, the compiler passes the size in bytes of the common block as declared in each routine to f90_dyncom, and then on to _FTN_ALLOC. The Fortran run-time library contains a default version of _FTN_ALLOC, which simply allocates the requested number of bytes and returns.
If you use the nonstandard extension having the common block of the same name declared with different sizes in different routines, you may get a run-time error depending on the order in which the routines containing the common block declarations are invoked.
You can now create your own routine to dynamically allocate common blocks, which is especially useful when you are sharing libraries. To use your own routine, you must specify the run-time function FOR__SET_FTN_ALLOC.