#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
#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
#282: wrong error message on lline length
------------------------------+---------------------------------------------
Reporter: utke | Owner: hlcm
Type: defect | Status: new
Priority: major | Milestone:
Component: SourceProcessing | Keywords:
------------------------------+---------------------------------------------
the logic in
PyFort/process_fort_stmt.py
hcm@483 39 if flow.inputLineLength != 0:
hcm@483 40 if jl[flow.inputLineLength:] != '':
hcm@483 41 print >> sys.stderr, "The following text is being cut
because the statement exceeded the specified line length:
"+jl[flow.inputLineLength:]
Is being applied *after* the line has been concatenated and the line
length of the concatenated line has nothing to do with the
intial linelength being assumed by default from the formal or
being specifcied by the user.
--
Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/282>
OpenAD <http://www.mcs.anl.gov/openad>
Bug tracking for OpenAD components
