May 2012 - 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] #283: wrong character length for function2subroutine temporary
by OpenAD 20 Jun '12

20 Jun '12

#283: wrong character length for function2subroutine temporary ---------------------------------+------------------------------------------ Reporter: utke | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Application - SCALE | Keywords: ---------------------------------+------------------------------------------ see PrePost/TestSources/f2sCharReturn.free.f90 -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/283> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

2 3

Re: [Ad-dev] Managed to build
by Sri Hari Krishna Narayanan 23 May '12

23 May '12

Kaveh, The latest revision has been developed with a lot more features that are used to support Fortran Input that may not work for the C side right now. Can you please try revision 631 or 587 with boost_1_43_0. I can provide better guidance for this. You should be able to upgrade to the latest version in a couple of weeks. Krishna On May 23, 2012, at 6:23 AM, Kaveh Vahedipour wrote: > I had to take the newest. 631 had another problem. Which I know how > to fix in tehory but didn't wanna find out how complicated it would > be in the end. Something about the compiler not knowing how to make > a boost::unorder_list or so to ... > > But I might know where the problem was anyways. It turns out that > angel just built the static library and make was happy if an error > had occured down the road and you thought that you had fixed it. > > I have > > 64bit precise pangelot > gcc-4.4 > rose-0.9.5a-18998 > xerces-2.8.0 > xaifBooster (rev 125) > angel (rev 82) > boost 1.46.1 > openanalysis 1.0 (svn) > > Cheers, > Kaveh. > > On 23 May 2012, at 12:46, Sri Hari Krishna Narayanan wrote: > >> Hi Kaveh, >> >> Can you tell me which revision of ADIC you checked out? >> >> Thanks, >> Krishna >> >> On May 23, 2012, at 4:15 AM, Kaveh Vahedipour wrote: >> >>> Dear ADIC team, >>> >>> I have done my best to get ADIC2 compiled. I have finally made it. >>> After many hours of trouble shooting code & build files. This is >>> on 64bit Linux, btw. >>> >>> However, this is the error that I am faced with now: >>> >>> <snip> >>> kvahed@beo-38 ~/ADIC/adic_source/tests/basic/exec/ >>> mini1_forward_array> make >>> make: Warning: File `Makefile' has modification time 97 s in the >>> future >>> >>> ==== Using ADIC to generate derivative code (forward-dense) >>> ======mini1_dense_forward.ad.c=== >>> /usr/local/bin/adic2 mini1.c -mforward --nary >>> ADIC DEBUG[Command Line][0]: ../adic_source/util/ >>> BoostCommandLine.cpp 271 ROSE command line arguments: -rose:c >>> mini1.c >>> ERROR: caught exception: (../adic_source/main/ADIC.cpp: >>> 322)LogicException: preprocessTemplateFile: no template file >>> named found >>> make: *** [mini1_dense_forward.ad.c] Error 255 >>> </snip> >>> >>> Do you have any suggestions as to how to proceed from here? >>> >>> With highest regards, >>> Kaveh Vahedipour. >>> >>> --- >>> Kaveh Vahedipour >>> Institute of Neuroscience and Medicine >>> Medical Imaging Physics >>> Forschungszentrum Juelich GmbH >>> 52425 Juelich >>> Germany >>> Phone: +49-2461-611921 >>> Fax: +49-2461-611919 >>> E-mail: k.vahedipour(a)fz-juelich.de >>> Web: http://www.fz-juelich.de/inm/inm-4 >>> >>> >>> >>> ------------------------------------------------------------------------------------------------ >>> ------------------------------------------------------------------------------------------------ >>> Forschungszentrum Juelich GmbH >>> 52425 Juelich >>> Sitz der Gesellschaft: Juelich >>> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 >>> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher >>> Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), >>> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, >>> Prof. Dr. Sebastian M. Schmidt >>> ------------------------------------------------------------------------------------------------ >>> ------------------------------------------------------------------------------------------------ >>> >>> Kennen Sie schon unseren neuen Film? http://www.fz-juelich.de/film >>> Kennen Sie schon unsere app? http://www.fz-juelich.de/app >> > > --- > Kaveh Vahedipour > Institute of Neuroscience and Medicine > Medical Imaging Physics > Forschungszentrum Juelich GmbH > 52425 Juelich > Germany > Phone: +49-2461-611921 > Fax: +49-2461-611919 > E-mail: k.vahedipour(a)fz-juelich.de > Web: http://www.fz-juelich.de/inm/inm-4 >

1 0

[openAD] #284: strings containing double quotes should have the quotes represented as '&quote; ' in xaif
by OpenAD 07 May '12

07 May '12

#284: strings containing double quotes should have the quotes represented as '&quote;' in xaif ---------------------------------+------------------------------------------ Reporter: utke | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: multiple components | Keywords: ---------------------------------+------------------------------------------ an example is given in Regression/testRoundTrip/examples/dQuoteInString -- Ticket URL: <http://trac.mcs.anl.gov/projects/openAD/ticket/284> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 0

[openAD] #282: wrong error message on lline length
by OpenAD 07 May '12

07 May '12

#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

1 2