[openAD] #264: dimension information dropped (set to 1) in some array declarations
#264: dimension information dropped (set to 1) in some array declarations ---------------------------------+------------------------------------------ Reporter: utke | Owner: Type: defect | Status: new Priority: major | Milestone: scale1 Component: Application - SCALE | Keywords: ---------------------------------+------------------------------------------ -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/264> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components
#264: dimension information dropped (set to 1) in some array declarations ---------------------------------+------------------------------------------ Reporter: utke | Owner: Type: defect | Status: new Priority: major | Milestone: scale1 Component: Application - SCALE | Keywords: ---------------------------------+------------------------------------------ Comment(by utke): for pxsset_I.f90 : integer , dimension(nptt,iftg) :: inemat we get: INTEGER(w2f__i4) INEMAT(1 : 1, 1 : 1) -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/264#comment:1> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components
#264: dimension information dropped (set to 1) in some array declarations ---------------------------------+------------------------------------------ Reporter: utke | Owner: Type: defect | Status: closed Priority: major | Milestone: scale1 Component: Application - SCALE | Resolution: duplicate Keywords: | ---------------------------------+------------------------------------------ Changes (by utke): * status: new => closed * resolution: => duplicate Comment: This is a duplicate of #224 rationale: INEMAT is a local variable in a module subroutine that contains another subroutine. The contained subroutine is elevated one level and the local variables of the containing subroutine that are used in the contained routine are elevated to module level. However nptt and iftg are themselves module variables and are not parameters and therefore cannot be used to declare the dimension of a module variable. The front end drops them to avoid the conflict and the default replacement with 1 kicks in. Workaround is to make all such variables part of the argument list to be passed to the contained subroutine -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/264#comment:2> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components
participants (1)
-
OpenAD