| Age | Commit message (Collapse) | Author | 
 | 
 | 
 | 
already dependent on it.
 | 
 | 
work)
 | 
 | 
FloatingPointOps.ll).
 | 
 | 
- You can now make tests disabled, or expected to fail, by writing something like:
     // XFAIL: llvm-3.4
   or
     // REQUIRES: not-llvm-3.4
 - This mechanism doesn't support version comparisons, it is mostly intended to
   help with switching over to new LLVM versions and incrementally working
   through the test failures.
 | 
 | 
- LLVM changed the exception handling semantics a lot, and we can't write
   compatible tests across the versions. Unfortunately I am afraid this probably
   also means KLEE's exception handling semantics are broken for LLVM 3.4+, but
   our C++ support is spotty at best. These tests should probably be replaced
   with ones in a source language that supports exceptions if and when someone
   wants to make that work.
 | 
 | 
 | 
 | 
- See comment, this is a gross workaround for Darwin's very small default limit
   on shared memory size. I'm not sure how big of a counterexample users can
   actually expect STP to solve in practice -- if there is a practical use for
   larger ones it would probably be good for us to write a fallback strategy.
 | 
 | 
not asserts.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
- This allows us to build in +Asserts mode even when LLVM isn't (by disabling
   the checks in that mode).
 - Eventually it would be nice to just move off of LLVM's DEBUG infrastructure
   entirely and just have our own copy, but this works for now.
 - Fixes #150.
 | 
 | 
Add TravisCI testing.
 - Needs various cleanups, but merging now so we can enable for the primary repository and continue iteration there.
 | 
 | 
Some additional cleaning in test/Makefile
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
unsupported floating point widths.
 | 
 | 
- The change in 6829fb9 caused us to not allocation InstructionInfo objects for
   instructions without source-level debug info, however, that means that all
   such instructions end up sharing the one dummy InstructionInfo object, which
   really breaks statistics tracking.
 - This commit basically reverts that change, and also changes the code so we
   don't ever use the dummy InstructionInfo object for instructions, so that
   this problem can't be hit in other ways (e.g., if someone modifies the module
   after the InstructionInfoTable construction). There is a FIXME for checking
   the same thing for functions.
 - Fixes #144.
 | 
 | 
- This ensures any stray klee-last files won't be picked up by my check to
   prevent people from adding tests that don't use --output-dir.
 | 
 | 
which the LLVM JIT can't handle.
 | 
 | 
 | 
 | 
path.
 - Otherwise this test takes a long time just hammering on the allocator trying
   to get to the memory limit.
 | 
 | 
- This one test was taking about half the test time, and it definitely isn't
   worth that much value as a test. We probably should have some kind of long
   running tests infrastructure for things where we actually want to test KLEE
   on real programs.
 | 
 | 
parallel.
 - It would be nice if there was an easier way to do this that didn't involve
   editing all of the tests (like running each test in its own directory), but
   this approach fixes #146 and doesn't involve changing 'lit' or writing a
   wrapper harness. My assumption is a lot of tests start are derived from
   another one, so hopefully following this convention won't be burdensome, and
   I updated 'make check' so that it will produce an error if any test runs klee
   without --output-dir (by checking for the existing of klee-last files).
 - This also helps with #147 but I still can't fully run tests in parallel (I
   start hitting STP errors).
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Fixes #96.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
function anymore.
 | 
 | 
 | 
 | 
 | 
 | 
unordered_{map,set} includes.
 - I'm not sure what the status of libstdcxx's c++11 support is. It may be we
   can just move over to <unordered_map> everywhere, but I don't have a Linux
   test machine handy at the moment.
 | 
 | 
 | 
 | 
config.h files.
 - There seems to be a better solution for this by defining a macro prefix, per:
     http://www.gnu.org/software/autoconf-archive/ax_prefix_config_h.html
   but I have no experience with that and it looks like it might involve
   rewriting a bunch of our macro checks.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
newer versions of autoconf""
The entire point of this version check in this script is so that configure is
only generated with one exact version of autotools, so that it doesn't get
spurious diffs from people generating it with different versions. This is the
approach used by LLVM, and I'd like to stick to it. Most people don't regenerate
these files, so it falls on the people who do to install the appropriate
versions of the tools.
If we want to change this policy, we should just drop the version checks completely.
 | 
 | 
klee-stats refactoring and improvement by antiAgainst: "this includes changing from OptionParser to ArgumentParser, rewriting not-pythonic code, respecting PEP8, etc; Adding line chart drawing in klee-stats."
 | 
 | 
 | 
 | 
Fix to avoid warning message taking address of main
 | 
 | 
 |