July 2010 - 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] #213: postProcess.py needs to add value selector (and do nothing else) for original function definitions that have been turned into subroutines
by OpenAD 31 Mar '11

31 Mar '11

#213: postProcess.py needs to add value selector (and do nothing else) for original function definitions that have been turned into subroutines ------------------------------+--------------------------------------------- Reporter: lyonsam | Owner: utke Type: defect | Status: new Priority: major | Milestone: scale1 Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- The issue is this: you know how we have postprocess and transformfile? I have a situation where there's a function in centrm (in centrm/psget_I.f90) that gets subroutinized by the preprocessor, so that both the function and the new subroutine go through the tool. As is usually the case when we do this, the subroutine will have active statements whereas the function will not (because we've replaced all the function calls that we've seen with subroutine calls, so the function isn't used in an active context). So far so good. In this case, though, the function uses a module variable that happens to be active, like {{{ passive1 = active*passive2 }}} where we would need {{{ passive1 = active%v*passive2 }}} So here's what we need: for function units, the postprocessor should do exactly what transformfile does (like adding the %v whenever an active variable is referenced), and none of the stuff that the postprocessor does on non-function units. -- Ticket URL: <http://trac.mcs.anl.gov/projects/openAD/ticket/213> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 2

[openAD] #224: open64 does not distinguish 1st and 2nd nesting level of SRs
by OpenAD 12 Oct '10

12 Oct '10

#224: open64 does not distinguish 1st and 2nd nesting level of SRs ------------------------------+--------------------------------------------- Reporter: utke | Owner: utke Type: defect | Status: new Priority: major | Milestone: Component: Open64 front end | Keywords: ------------------------------+--------------------------------------------- Open64 parser does not mark up bar as being nested in foo for module m contains subroutine foo () .... contains subroutine bar() .... -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/224> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 7

[openAD] #202: insufficient parsing of rewind statements
by OpenAD 09 Sep '10

09 Sep '10

#202: insufficient parsing of rewind statements ------------------------------+--------------------------------------------- Reporter: lyonsam | Owner: lyonsam Type: defect | Status: new Priority: minor | Milestone: Component: SourceProcessing | Keywords: ------------------------------+--------------------------------------------- occuring in centrm/pxlib_read_M.f90 (we were able to get around this for now because we dont really need to transform this file): rewind ['(', 'linpxs', ')'] -- Ticket URL: <https://trac.mcs.anl.gov/projects/openAD/ticket/202> OpenAD <http://www.mcs.anl.gov/openad> Bug tracking for OpenAD components

1 4

[ADIC] #44: Shenzhen Taijie Printing Company in China
by ADIC 26 Jul '10

26 Jul '10

#44: Shenzhen Taijie Printing Company in China -------------------------------+-------------------------------------------- Reporter: Printing in China | Owner: narayanan Type: defect | Status: new Priority: major | Milestone: Component: Canonicalization | Version: Keywords: printing china | -------------------------------+-------------------------------------------- Taijie Printing is a [http://www.china-printing.org/ Printing Company in China] specialized in printing all kinds of printed products, We have more than 10 years experiences in Packaging [http://www.china-printing.org/ Printing in China]; our products including labels, books, catalogs, magazines, calendars, brochures, notebooks, posters, packing materials, advertising collateral, gifts related, CD's and DVD's , etc. Shenzhen Taijie Printing CO. Ltd. Rm 323, Bldg 526, 2nd Bagua Rd, Futian Dist., Shenzhen, 518003 China. Website: [http://www.china-printing.org/ http://www.china-printing.org] -- Ticket URL: <http://trac.mcs.anl.gov/projects/ADIC/ticket/44> ADIC <http://trac.mcs.anl.gov/projects/ADIC> ADIC: Automatic Differentiation for C and C++

1 0

[ADIC] #40: replace debugMsg with a nice macro
by ADIC 23 Jul '10

23 Jul '10

#40: replace debugMsg with a nice macro -------------------------+-------------------------------------------------- Reporter: utke | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Utilities | Version: Keywords: | -------------------------+-------------------------------------------------- one of the few things that macros are good for... part of the problem is stuff like this: debugMsg(5, "FILE : " + sg->unparseToString()); The argument "FILE : " + sg->unparseToString() is ALWAYS evaluated regardless of the debug level I specify on the command line. If you replace this with a nice macro like the openad/f one: #define DBG_TAG_MACRO(Group,Tag,StreamArgs) \ if (DbgLoggerManager::instance()->isSelected((Group)) && DbgLoggerManager::instance()->wantTag((Tag))) { \ std::ostringstream aLoNgAnDwEiRdLoCaLnAmeFoRtHiSmAcRoOnLy; \ aLoNgAnDwEiRdLoCaLnAmeFoRtHiSmAcRoOnLy << StreamArgs << std::ends; \ DbgLoggerManager::instance()->logDebug(__FILE__,__LINE__,(Group),aLoNgAnDwEiRdLoCaLnAmeFoRtHiSmAcRoOnLy,(Tag)); \ } you not only avoid evaluating the arguments but also get automatically __FILE__ and __LINE__ injected. Wouldn't that be nice? -- Ticket URL: <http://trac.mcs.anl.gov/projects/ADIC/ticket/40> ADIC <http://trac.mcs.anl.gov/projects/ADIC> ADIC: Automatic Differentiation for C and C++

1 2

[ADIC] #42: adic2 binary not located in standard spot causes odd assumptions for intrinsic file location
by ADIC 23 Jul '10

23 Jul '10

#42: adic2 binary not located in standard spot causes odd assumptions for intrinsic file location -----------------------------+---------------------------------------------- Reporter: utke | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: OA/Sage to XAIF | Version: Keywords: | -----------------------------+---------------------------------------------- e.g. by accident running /ADIC_build/.libs/adic2 gives Fatal Error at file , line 0, char 0 Message: unable to open primary document entity '/sandbox/Argonne/Dev/RoseFE/ADIC_build/share/inlinable_intrinsics.xaif' -- Ticket URL: <http://trac.mcs.anl.gov/projects/ADIC/ticket/42> ADIC <http://trac.mcs.anl.gov/projects/ADIC> ADIC: Automatic Differentiation for C and C++

1 2

[ADIC] #43: use of date in build
by ADIC 23 Jul '10

23 Jul '10

#43: use of date in build ---------------------------------+------------------------------------------ Reporter: utke | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Configuration/Build | Version: Keywords: | ---------------------------------+------------------------------------------ I get under opensuse 11.2: gmake[3]: Leaving directory `/sandbox/Argonne/Dev/RoseFE/ADIC_build/runtime' gmake[3]: [.version] Error 1 (ignored) date: invalid option -- 'v' Try `date --help' for more information. -- Ticket URL: <http://trac.mcs.anl.gov/projects/ADIC/ticket/43> ADIC <http://trac.mcs.anl.gov/projects/ADIC> ADIC: Automatic Differentiation for C and C++

1 2

[ADIC] #41: Usage of unparseToString for non-debugging purposes
by ADIC 19 Jul '10

19 Jul '10

#41: Usage of unparseToString for non-debugging purposes ------------------------------+--------------------------------------------- Reporter: snarayan | Owner: snarayan Type: enhancement | Status: new Priority: major | Milestone: Update to ROSE version 0.9.x Component: Canonicalization | Version: 2.0 Keywords: | ------------------------------+--------------------------------------------- There are instances of unparseToString that have been replaced by ESSENTIALUNPARSETOSTRING_MACRO. The usage of unparseToString for non- debugging purposes must be discontinued. -- Ticket URL: <http://trac.mcs.anl.gov/projects/ADIC/ticket/41> ADIC <http://trac.mcs.anl.gov/projects/ADIC> ADIC: Automatic Differentiation for C and C++

1 0