SageInterface: appendStatementList() should not skip stmt with NULL parent
(support boost 1.48) Fix #88
* using constructor instead of operator= for a hiddenlist usage
(support boost 1.48) Fix #88
* using constructor instead of operator= for a hiddenlist usage
(configure error) Adrian fixed this problem

Conflicts:
	config/support-swipl.m4
(SageInterface::findFunctionDeclaration)
* correctly handle the isDefining flag
minor fix
(minor) have to cast type
(XOMP instrumentation)
* generate timestamp and sequential/parallel indicators for gnuplot
(XOMP) add region instrumentation support
* used to plot sequential and parallel execution of an OpenMP program
* controllable by environment variable "export XOMP_REGION_INSTR=1|0"
(XOMP) support passing file location info of parallel regions to runtime
* useful for runtime instrumentation with source level location info.
(OpenMP Accelerator Model)
* initial parsing support for target directive and device/map clauses

Conflicts:
	src/frontend/SageIII/ompparser.yy
(OpenMP accelerator) parse lower and upper bound dimension info for array variables in map clause
* extend variable_list to allow optional dimension info. in parser
* store dimension info into std::map<SgSymbol*,  std::vector < std::pair <SgExpression*, SgExpression*> > > array_dimensions in OmpAttribute

Conflicts:
	src/frontend/SageIII/ompparser.yy
(OpenMP Accelerator) add new IR nodes for "omp target" and its clauses
(OpenMP Accelerator) IR creation and unparsing for "omp target"
(OMP ACC) added one more test case
* skip SageInterface::clearUnusedVariableSymbols() in AST consistency
 test since #define N 100 will cause a fake symbol for N be created with
 unknowntype
* SageBuilder: set parent for the fake symbol

Conflicts:
	src/frontend/SageIII/sageInterface/sageBuilder.C
fixed a few conflicts
(OMP ACC) first set of translations for omp for loops under "omp target"
(OMP ACC) cleanup outliner code, start kernel extraction
(outliner) refactor the generation of function call parameter list
* separate two cases into two functions:
   parameter wrapping vs. individual parameters
* clarify the handling of original form vs. addressOf form
(outliner) cleanup and documentation