~cnx/klee - KLEE fork for patch differentiation testing

Age	Commit message (Collapse)	Author
2019-03-05	workaround for LLVM PR39177	Julian Büning
	provides a workaround for LLVM bug PR39177, which affects LLVM versions 3.9 - 7.0.0: https://bugs.llvm.org/show_bug.cgi?id=39177 This commit is intended to be reverted once support for LLVM versions <= 7 is dropped from KLEE.
2018-09-14	cmake: find_llvm, fix libraries with llvm-config 3.9	Jiri Slaby
	llvm-config from llvm 3.9 was broken. Fix handling of improperly returned libraries. From: liblibLLVM-3.9.so.so To: libLLVM-3.9.so Fixes #895. Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
2018-07-02	CMake: use cmake_{push,pop}_check_state	Julian Büning

2018-06-11	cmake: find_llvm, handle libLLVM-version.so properly	Jiri Slaby
	Some builds of llvm contain a lib like this: /usr/lib64/libLLVM-3.9.so Extend the regular expression, so that we really return what we are supposed to. Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
2017-10-17	[cmake] detect available metaSMT backends using a pre-defined flag and raise ↵	Hoang M. Le
	compile flags accordingly
2017-07-28	[CMake] Change the default value of `ENABLE_SOLVER_METASMT` to be set	Dan Liew
	dynamically based on whether MetaSMT is available. Previously the default was always off.
2017-07-28	[CMake] Refactor Z3 detection and change the default value of	Dan Liew
	`ENABLE_SOLVER_Z3` to be set dynamically based on whether Z3 is available. Previously the default was always off.
2017-07-28	[CMake] Refactor STP detection and change the default value of	Dan Liew
	`ENABLE_SOLVER_STP` to be set dynamically based on whether STP is available. Previously the default was always off.
2017-07-25	[CMake] Fix bug where we would inherit LLVM's `-DNDEBUG` define	Dan Liew
	when LLVM was built without assertions. This prevented `ENABLE_KLEE_ASSERTS` from working correctly. Reported by @MartinNowack .
2017-03-30	[CMake] Try to fix bug reported by #633.	Dan Liew
	It looks like older LLVM versions that were built from SVN/git didn't have a patch version number (i.e. `3.4svn` rather than `3.4.0svn`).
2017-03-23	remove special handling of metaSMT_CXXFLAGS (unnecessary now as we use a ↵	Hoang M. Le
	fixed version of metaSMT with this flag being properly set)
2017-01-28	[cmake] add PATH_SUFFIXES needed to find z3 on Fedora	Kevin Laeufer

2016-12-19	[CMake] Fix linker warning about mixed linking modes when LLVM was	Dan Liew
	built with `-fvisibility-inlines-hidden`. This was observed when using a bottled version of LLVM 3.4 on macOS that appears to have been built with this option.
2016-12-18	CMake: Fixed the LLVM version regex	Adrian Herrera
	When trying to KLEE with a version of LLVM (specifically, 3.5) built from Github (https://github.com/llvm-mirror/llvm/tree/release_35) the regex in find_llvm.cmake failed to match the LLVM version string because it was suffixed with "svn" - i.e. "3.5.2svn". Added the optional "svn" suffix to the CMake regex to fix this.
2016-11-22	[CMake] Fix determining the system libraries needed by LLVM from	Dan Liew
	`llvm-config` when using LLVM 3.5 and newer. In newer versions of `llvm-config`, `--ldflags` doesn't give the system libraries anymore. Instead we need to use `--system-libs`. Issue reported by @ryosa .
2016-11-22	[CMake] Fix link order of LLVM libraries and required system libraries.	Dan Liew
	Now LLVM libraries are added as imported targets and their link dependencies are explicitly stated so CMake can get the link order correct.
2016-11-21	[CMake] Fix the build when `-DBUILD_SHARED_LIBS=ON` is passed.	Dan Liew
	This fixes issue #507. We can't build the components as shared libraries right now due to cyclic dependencies (see #502 for a fix) and there are a few other patches needed too (see #507). Building the components as shared libraries isn't really desirable anyway because it would require us to ship KLEE's libraries which don't have a stable API.
2016-11-07	[CMake] Report git revision information if available.	Dan Liew
	This is done as a separate commit because it imports third party code. It's under the Boost license though so it "should be" fine.
2016-11-07	Implement a CMake based build system for KLEE.	Dan Liew
	This is based off intial work by @jirislaby in #481. However it has been substantially modified. Notably it includes a separate build sytem to build the runtimes which is inspired by the old build system. The reason for doing this is because CMake is not well suited for building the runtime: * CMake is configured to use the host compiler, not the bitcode compiler. These are not the same thing. * Building the runtime using `add_custom_command()` is flawed because we can't automatically get transitive depencies (i.e. header file dependencies) unless the CMake generator is makefiles. (See `IMPLICIT_DEPENDS` of `add_custom_command()` in CMake). So for now we have a very simple build system for building the runtimes. In the future we can replace this with something more sophisticated if we need it. Support for all features of the old build system are implemented apart from recording the git revision and showing it in the output of `klee --help`. Another notable change is the CMake build system works much better with LLVM installs which don't ship with testing tools. The build system will download the sources for `FileCheck` and `not` tools if the corresponding binaries aren't available and will build them. However `lit` (availabe via `pip install lit`) and GTest must already be installed. Apart from better support for testing a significant advantage of the new CMake build system compared to the existing "Autoconf/Makefile" build system is that it is not coupled to LLVM's build system (unlike the existing build system). This means that LLVM's autoconf/Makefiles don't need to be installed somewhere on the system. Currently all tests pass. Support has been implemented in TravisCI and the Dockerfile for building with CMake. The existing "Autoconf/Makefile" build system has been left intact and so both build systems can coexist for a short while. We should remove the old build system as soon as possible though because it creates an unnecessary maintance burden.