August 2011 - Ad-dev - mailman3.cels.anl.gov

[openAD] #200: introduce scope per CFG node
by OpenAD 18 Nov '14

18 Nov '14

#200: introduce scope per CFG node -------------------------+-------------------------------------------------- Reporter: utke | Owner: snarayan Type: enhancement | Status: new Priority: major | Milestone: Component: xaif | Keywords: -------------------------+-------------------------------------------------- for C++, with default scope being the same scope as the top level cfg scope for C/fortran -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/200> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 5

[openAD] #220: COMMON block symbol reference ambiguity in whirl
by OpenAD 22 Feb '13

22 Feb '13

#220: COMMON block symbol reference ambiguity in whirl --------------------------+------------------------------------------------- Reporter: utke | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: OpenADFortTk | Keywords: --------------------------+------------------------------------------------- for the following situation: subroutine foo () common /g/ v ... call bar() end subroutine subroutine bar() common /g/ v/ ... end subroutine the global whirl symbol table has 2 entries for 'v' (and also 'g'), one for each PU in which v is used. The association is done via the base ST of 'v' first to its corresponding 'g' and then that one's corresponding base symbol is either 'bar' or 'foo'. Normally the uses of the different incarnations do not overlap. However, the side effect analysis reports cumulative side effects in "foo" including sideeffects of 'bar' on bar's version of 'v' such that in foo now implicitly separate references occur (for checkpointing code) of both 'v' instance and that in turn leads to a duplication of the common block declaration in the unparser because there is no logic that can turn bar::v into the equivalent foo::v to avoid the bogus reference. This will have to be fixed either in OpenADFortTk or in whirl2f. -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/220> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 5

[openAD] #279: allocation of propagation variables is not done in the adjoint
by OpenAD 11 Jan '12

11 Jan '12

#279: allocation of propagation variables is not done in the adjoint -------------------------+-------------------------------------------------- Reporter: lyonsam | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: xaifBooster | Keywords: -------------------------+-------------------------------------------------- the allocation is mistakenly printed in the taping version -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/279> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 2

[openAD] #280: function2subroutine: nested interfaces are handled incorrectly
by OpenAD 29 Aug '11

29 Aug '11

#280: function2subroutine: nested interfaces are handled incorrectly ------------------------------+--------------------------------------------- Reporter: utke | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- see the SourceProcessing test case f2sFuncAsDummy3 -- Ticket URL: <http://trac.mcs.anl.gov/projects/openAD/ticket/280> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 0

[openAD] #277: function2subroutine: cover dummy function pointers
by OpenAD 29 Aug '11

29 Aug '11

#277: function2subroutine: cover dummy function pointers ------------------------------+--------------------------------------------- Reporter: utke | Owner: utke Type: enhancement | Status: new Priority: major | Milestone: Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- see PrePost/TestSources/f2sFuncAsDummy* for examples -- Ticket URL: <http://trac.mcs.anl.gov/projects/openAD/ticket/277> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 2

[openAD] #278: array allocation bounds for passives shaped after actives
by OpenAD 29 Aug '11

29 Aug '11

#278: array allocation bounds for passives shaped after actives ------------------------------+--------------------------------------------- Reporter: lyonsam | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: SourceProcessing | Keywords: postprocessing allocation ------------------------------+--------------------------------------------- example: {{{ double precision, dimension(size(x)) :: z }}} after postprocessing is {{{ REAL(w2f__8) Z(1 : INT(SIZE(__value__(X)))) }}} -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/278> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 1