fix Issue 12809 - More strict nothrow check for try-finally statement
fix Issue 11542 - scope(failure) messes up nothrow checking
improve test case for 4082
fix Issue 3032 - No stack allocation for "scope c = new class Object {};"
Merge pull request #3593 from 9rnsr/fix3032

Issue 3032 - No stack allocation for "scope c = new class Object {};"
Make warning flags in src/posix.mak appear on one line each

This makes it eaiser to see which warning flags are enabled and also
disable/add/remove flags. Only a single line of text per flag will be
touched this way.
Re-allow using delegate.ptr and .funcptr as lvalues
Merge pull request #3596 from yebblies/dglvalue

Re-allow using delegate.ptr and .funcptr as lvalues
fix 879 - support for --gc-sections

- pin .deh_eh and .minfo by emitting fake references in dso startup code

- enable --gc-sections linker switch
Merge pull request #3595 from andron/stylish-warning-flags

Make warning flags in src/posix.mak appear on one line each
Merge pull request #3597 from MartinNowak/fix879

fix 879 - support for --gc-sections
Merge pull request #3592 from 9rnsr/fix11542

Issue 11542 & 12809 - Improve blockExit calculation on try-catch-finally statement
Do implicit cast for ExpInitializers inside CTFE

Move the implicit cast inside CTFE, so that we're evaluating the
final value.
Fix bug 7209: Stack overflow on circular enum with explicit type

Detect the error in the semantic pass. This slightly changes the error
message for one existing test (it was previously detected inside CTFE)
-- now the *first* circular definition generates the error, which makes
more sense.
Fix float precision in one compile-time test

This test doesn't work if there is floating point round-off error.
Fix bug 9937 CTFE floats don't overflow correctly

This fixes the bug in comment 4 of bug 9937.
Although CTFE floats may use higher precision than is available on the target
machine, it is impossible for that extra precision to survive to runtime.
This commit forces the extra bits to be discarded at the end of CTFE, rather
than in the glue layer. This eliminates the bizarre anomalies in bug 9937 where
a variable has two values at the same time (!) It also opens the way for CTFE
to calculate with much higher precision than is available at runtime.