Allow passing arbitrary command line flags to klee and kleaver
when running llvm-lit. This is done by doing something like

$ cd test/
$ llvm-lit --param klee_opts=--xxx --param kleaver_opts=--yyy .

This would pass "--xxx" as an extra option to KLEE when running
tests and would pass "--yyy" as an extra option to kleaver when
running tests.

This feature has been added to make it easy to pass different flags to
KLEE or Kleaver without needing to modify tests or recompile KLEE with
different defaults (yuck!).
Add support for archive and single bc file linking

With LLVM 3.3 the linker does not support reading of
archive files directly. This brings the support back
(based on llvm-mn).
Furthermore, linking single bc files or archives with
bc and object files mixed is supported as well.
Improved archive (of bitcode modules) linking performance for
LLVM >= 3.3 by effectively reimplementing the linking algorithm
used in LLVM <= 3.2.

The LLVM specific bitcode archive format has been removed
from LLVM >= 3.3 . Now archives are normal system archives that can
contain LLVM bitcode modules as well as regular binary object files.

The previous commit implemented an approach where ALL the bitcode
modules get linked in which can be terribly slow when klee-uclibc gets
linked (~600 LLVM modules).

Here are the options that I considered to address this:

* Use LD with LLVM gold plug-in and call as an external program.
  I Don't really want to add another dependency to KLEE. It already
  has enough!

* Use the upcomming LLVM linker (lld). Not really an option
  because at the time of writing there is no support for linking
  archives of bitcode modules.

* Don't use archives at all and just work with modules (i.e.
  replace uses of llvm-ar with llvm-link and tinker with the
  flags a little). This isn't so great because the resulting
  LLVM bitcode module we execute is bigger than it should be.

* Reimpelent bitcode archive linking ourselves in a slightly
  better way.

I've gone for the last option

This implementation unfortunately loads all bitcode modules into memory
first so we can query the module symbols tables. I would prefer to read
the archive's index and link in modules on demand but unfortunately
although the new Object::Archive interface in LLVM allows iteration over
symbols it doesn't provide a way of knowing if that symbol is
defined/undefined.

This implementation is far from perfect!
Do not consider llvm intrinsics as undefined symbols in KLEE's
bitcode archive linker.
Implement const_iterator interface for SpecialFunctionHandler so
that clients can access HandlerInfo nicely.
When using KLEE's built-in Bitcode archive linker do not consider
KLEE intrinsics as undefined symbols
Fix access of iterators after they have been invalidated

Iterators get invalidated after elements of std::vector/set are
deleted. Avoid this by remembering which elements need to be
deleted and do it after iterating over the data structure.
Merge pull request #100 from delcypher/pass-param-llvm-lit

Allow passing arbitrary command line flags to klee and kleaver when running llvm-lit
Correct and tidy up comments.
Refactor variable name s/RemovedSymbols/SymbolsToRemove/
because "RemovedSymbols" implies that the symbols have already been
removed which is misleading because we don't remove until the end.
Refactor cleaning up memory in linkBCA() so that if linking fails
then clean up is performed.
When running with -debug-only=klee_linker do not report the number
of modules left because this information is no longer correct
(we no longer shrink the vector).
Merge pull request #70 from MartinNowack/feature_reading_archive

Add support for archive and single bc file linking