David Lindauer

run the libcxx tests

142

run the libcxx tests and add an appveyor build to run them as well,

the backend generates spurious setne instructions... get rid of them where possible

investigate what happens when destructors at the end of a function are inlined. It seems like some spurious code is generated, for example in min_alloc::operator ==

Right now, function parameters are spilled to memory during inlining. Improve this so that when possible, the values can be kept in temporary registers.

Clean up type handling

1

get rid of bt_const, bt_volatile, and other similar qualifiers, using flags on the type instead. This will speed up the compiler, and use less memory at compiler time.

Use less temp variables

1

if you do something like this: ``` #define MYCODE \ { \ /* declare some vars */ \ /* do something slightly complicated, maybe a loop or maybe function calls...

Rewrite OCC symbol tables

2

The OCC Symbol table processing is one of the biggest single remaining uses of CPU time. It averages between 5 and ten percent of the compile time for typical C++...

travis-ci build

45

now that github can trigger travis-ci builds again, write a build-script for the travis-ci build. this is ONLY to build once with an alternate compiler and is not intended to...

when compiled with /C-E dtoa.c gives erroneous output. For example when running ELLF.EXE from the tests.

Coverity scan, compilers

5

Coverity scan on occ, occil, occpr, and C-style preprocessor