Remove boilerplate code (jump* methods in Compiler)
Remove boilerplate code (general binaryOp methods in Compiler)
Remove boilerplate code (float binaryOp methods in Compiler)
only enable LTO if use-lto is true

When using clang, as with GCC, we shouldn't use LTO if the developer
has specified use-lto=false.
Specify formatting style via .clang-format config file
Merge pull request #140 from dicej/master

only enable LTO if use-lto is true
Remove boilerplate code (unaryOp methods in Compiler)
Remove boilerplate code (nullaryOp methods in Compiler)
Remove redundancy in compiling arithmetic operations
Remove redundancy in compiling jump operations
Reformat a few extra-long lines
Extract independent runtime thunks into their own file
Merge pull request #142 from joshuawarner32/compiler-boilerplate

Remove boilerplate in Compiler interface
Merge pull request #141 from joshuawarner32/clang-format

Specify formatting style via .clang-format config file
Added the easy to add interfaces and implementations for java.util.concurrent to pave the way for future expansion of avians java.util.concurrent classpath implementation.
Fix for spelling error joel pointed out, as well as a simple unit test around the TimeUnit conversions
Merge pull request #143 from jentfoo/concurrency_classpath_extension

Expanding avian's classpath for java.util.concurrent
fix uninitialized value warning in compile.cpp

Clang was complaining that newIp might be used uninitialized at the
bottom of our giant, unstructured compile loop, so I initialized it
with a bogus value, which means it will at least fail consistently if
Clang is right and there really is a path by which that code is
reached without otherwise initializing newIp.
remove obsolete idle statement from Unsafe.getLongVolatile

Now that Josh has fixed the busy block bug (see commit 10d15d2), we
don't need this anymore.
implement Unsafe.putOrderedLong and putVolatileLong

The former just defers to the latter for now, since it provides
strictly weaker guarantees.  Thus it's correct to use full
volatile-style barriers, though not as efficient as it could be on
some architectures.