Make guessing the target an info instead of a warning

Having this as a warning makes IDEs to go to the Makefile where the
warning was issued as if an error occurred, which is rather annoying for
something is really normal. An info is enough to let the user now how
the target was guessed.
cod2: Fix latent instruction reorder bug in cdmemcmp

Triggered on Linux by test81 in interpret.d with the
array comparison optimization patch.
Optimize simple array comparison (Issue 9477)
fix Issue 9790 - Internal error when compiling a invalid variable in template

1. Remove gagging in VarDeclaration::semantic
2. Commit type in StructLiteralExp::castTo like as StringExp and NullExp
   It's necessary to avoid std.traits unittest breaking.
fix Issue 9818 - Constant folding for static array does not work with initializing by element

Refactoring code for initializer semantic.

- Handle implicit constructor call in ExpInitializer::semantic
- Add target type parameter in Initializer::toExpression.
  For `T[n] sa = e;`, its initializer translation to [e1, e2, ..., en] is delayed until it's really needed.
Fix issue 9744 Poor error message taking address of thread-local variable at compile time

Move the error message from the glue layer, into the interpreter.
Also fix an incorrect entry point into the glue layer.
Fix issue 9745 Allow &staticvar in CTFE

Use SymOffExp for non-dereferenceable pointers to static variables.
It's already supported in the const-folding code, now support it in
CTFE as well. This commit adds full support for pointer arithmetic.
Allow pointer type-painting for pointers to global variables
Allow == comparison of absolute address pointers

They are mainly fake pointers, eg as used for Windows HANDLEs.
Comparison is allowed in const-folding, should be valid in CTFE too.
fix Issue 9788 - -profile doesn't work if exceptions are thrown in the running program
replace VolatileStatement with SynchronizedStatement
[Refactoring] Separate side-effect part in TupleExp

It had been implicitly contained in `te->exps[0]`, but it wasn't flexible design.
Factoring out the part to `TupleExp::e0` will make the design and code clean
Merge pull request #1797 from leandro-lucarella-sociomantic/cpu-warn-to-info

[trivial] Make guessing the target an info instead of a warning
Merge pull request #1801 from 9rnsr/fix9818

Issue 9818 - Constant folding for static array does not work with initializing by element
Merge pull request #1815 from WalterBright/removeVolatile

replace VolatileStatement with SynchronizedStatement
Merge pull request #1763 from donc/ctfeStaticPtr9745

9744 and 9745: allow taking address of static variables in CTFE
optimize out dead catches
Merge pull request #1810 from WalterBright/rmdeadcatches

optimize out dead catches
Merge pull request #1812 from 9rnsr/refactor_tuple

[Refactoring] Separate side-effect part in TupleExp
Merge pull request #1766 from CyberShadow/fix9477

Optimize simple array comparisons (Issue 9477)