April 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

Re: [Ad-dev] [openAD] #111: posprocessor ( and transformFile): initialization in activated type for DATA
by OpenAD 27 Apr '11

27 Apr '11

#111: posprocessor ( and transformFile): initialization in activated type for DATA ------------------------------+--------------------------------------------- Reporter: Utke | Owner: hlcm Type: defect | Status: assigned Priority: 3 | Milestone: Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- Comment(by hlcm): The following is acceptable syntax & compiles successfully with nagfor: module m public :: mType type mType integer:: c1 integer:: c2=0 end type end module program p use m type(mType) :: x=mType(2,1) type(mType) :: v data v%c1/2/ print*, x,v end program Therefore it would be possible to explicitly initialize only the value component of the active type and leave the default-initialized derivative component alone. For a more complicated case, it would be possible to make a transformation for a structure s with components a, b & c where b becomes active in the following manner data s / 1,2,3 / data s%a, s%b%v, s%c / 1,2,3 / However it may not be worth the effort until a problem arises -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/111#comment:5> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 0

Re: [Ad-dev] [openAD] #137: consolidate behavior for I/O of active variables
by OpenAD 21 Apr '11

21 Apr '11

#137: consolidate behavior for I/O of active variables --------------------------+------------------------------------------------- Reporter: Utke | Owner: utke Type: defect | Status: accepted Priority: 3 | Milestone: Component: OpenADFortTK | Keywords: --------------------------+------------------------------------------------- Comment(by utke): The decorators are added now so readWrite1 works but in readWrite2 there still is a problem for the READ statement: read(3,'(EN26.16E3,EN26.16E3)') x . X is an array and to read it in, the use of X%V would imply the construction of a temporary array passed to the READ call, i.e. the X components wouldn't actually be populated. -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/137#comment:3> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 0

[openAD] #245: DATA stmt: allow (object , value) pairs to not be separated by comma
by OpenAD 18 Apr '11

18 Apr '11

#245: DATA stmt: allow (object , value) pairs to not be separated by comma ------------------------------+--------------------------------------------- Reporter: utke | Owner: utke Type: enhancement | Status: new Priority: major | Milestone: Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- for a complete implementation of the syntax spec (R532) which says the comma between the pairs is optional -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/245> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 4

[openAD] #233: parser fails on labeled do
by OpenAD 05 Apr '11

05 Apr '11

#233: parser fails on labeled do ------------------------------+--------------------------------------------- Reporter: utke | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- test case is PrePost/TestSources/UnStruct_controlflow_loop4.free.f90 -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/233> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 1