RFC: Fixes issue 3453, string literal input formats for Int128 & Uint128
Remove quoting from @int128_str & @uint128_str
static compiling prototype

Based on:
Squash reloadso changes for cleaner history
Sanitize macro names in llvm to avoid implied symbol
Re-add jl_dump_bitcode and clean up debugging code
generate llvm global variables for most literal_pointer_val
switch to llvm-managed global variables, load and save them
get much further in the static compile boot process
(barely) working static-compiled repl
static compiling
remove dependence on llvm-mangled names, improve Makefile rules
find sys.so relative to sys.ji
Merge branch 'master' of git://github.com/JuliaLang/julia into int128
Modify the parser to allow Int128, Uint128, BigInt literals
Add tests for Int128, Uint128, BigInt literal input
Fix mistake making all large integer literals negative
Change int128, uint128, BigInt function calls in parser to macro calls
Fix error with negative Uint128 literals
Make bin, oct, hex literals in the BigInt range into BigInts (were Uint128s)
Add tests for bin, oct, hex literals in the BigInt Range
Add tests for negated large unsigned literals
create a valid sys.dylib file for any compile

renames the --bare [-b] flag to --build
the --build flag now requires an argument (where to save the system image)
the build flag triggers mode selection so that the code can get correctly generated and saved
better error messages for literal_pointer_val in ccall
cleanup some elements of static compile, based on Jeff's comments. Also
partially address some minor issues with getopt usage miscounting the arguments
make static_compile build work on linux
try to make travis happy with static_compile
partial windows compatibility