On 22 March 2015 at 21:03, Cristian Cadar c.ca...@imperial.ac.uk wrote:
I think there is some rationale for having that code there, as we have
found it useful to have finer-grained control over optimisations in KLEE
in order to improve performance.
You can run all LLVM optimisations outside of
Hi,
There was some discussion about linking in Klee earlier on github
(https://github.com/klee/klee/pull/141). My preference is to remove all
linking from Klee. A provided wrapper script can do the necessary linking
using llvm-link and possibly some opt calls for internalization of functions
this adaption
already?
My first goal is to get klee compiled, then send the necessary patches to some
knowledgable person for review and possible inclusion.
Has there even been a decision to never upgrade to llvm-3.6?
Thanks, Heiko
___
klee-dev
for review and possible inclusion.
Has there even been a decision to never upgrade to llvm-3.6?
Thanks, Heiko
___
klee-dev mailing list
klee-dev@imperial.ac.uk mailto:klee-dev@imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/klee
