similar to: [LLVMdev] problems building llvm-gcc-4.2 on fedora 21

Hi I need a concolic execution framework based on LLVM. As far as I know, KLEE might be the best choice. However, KLEE(the stable version) is based on LLVM 3.4. I compiled my code with the latest LLVM, whose version is 7.0. Anyone know whether the bitcode could be used by KLEE. Or do I have to compile with the old version of LLVM again. Furthermore, if you have any other concolic execution

Hi all, can I access the numeric limits of the llvm types, e.g. HalfTy, FloatTy, DoubleTy, etc. in a fashion like the std numeric_limits tool? std::numeric_limits<half>::min() std::numeric_limits<half>::max() In c++API, I want to initialize values and need to know the correct range for the llvm types.... Thx Alex

On Tue, 4 May 2004, Finn S Andersen wrote: > Chris wrote in a followup: > > > Can you send the output of 'llc -o - foo.bc -debug -print-machineinstrs'? > > > Attached as "linscan". (But added the "-regalloc=linearscan" to provoke > the error). Yes, that's exactly what I meant... thanks for reading my mind! :) It looks like this is where

Hello, In my reading over the last couple of days, I have read that in order for klee to work with "native" Linux programs, I need to install the uClibc posix support for klee. I am not finding the uClibc source in the llvm svn repository anywhere. Is this still necessary for testing native Linux applications, and if so, where do I get the uClibc source to compile? Thanks in

Are there any "current" Linux distros that have installable packages for llvm, clang, nad klee? I am struggling to get klee built and need a working klee setup asap. Thanks in advance, Donald

On Fedora 17 I have installed a the binary clang package clang3.0-14. When I tried to build the latest llvm/clang from source using this binary clang I get essentially two different errors: 1) In file included from /home/fceldiener/vcs/llvm/include/llvm/Support/SwapByteOrder.h:20: /usr/bin/../lib/gcc/x86_64-redhat-linux/4.7.2/../../../../include/c++/4.7.2/limits:1404:27: error: use of

On Thu, May 06, 2004 at 04:06:27PM +0200, Finn S Andersen wrote: > Chris Lattner wrote: > > >I think that we should switch to C constants in this case. Can you try > >#include <math.h> and use HUGE_VAL instead? > > > It works: > > [finna at coplin11 ~/test]$ cat tst.cpp > #include <limits> > #include <iostream> > #include

Hi, I'd really appreciate some pointers in this regard. Regards, Kashyap On Wed, Oct 16, 2013 at 5:43 PM, C K Kashyap <ckkashyap at gmail.com> wrote: > Sorry ... I missed mentioning the details - > > this is the error I get - > > root at no1slu398:~/Documents/LLVM/tmp# clang++ -std=c++0x hello.cpp > In file included from hello.cpp:1: > In file included from >

Sorry ... I missed mentioning the details - this is the error I get - root at no1slu398:~/Documents/LLVM/tmp# clang++ -std=c++0x hello.cpp In file included from hello.cpp:1: In file included from /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/thread:38: /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/chrono:535:6: error: no matching constructor for initialization of

On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote: > Moving to LLVM dev to discuss the possibility of extending the cast > infrastructure to handle this. > > On Tue, Nov 20, 2012 at 5:51 PM, John McCall <rjmccall at apple.com> wrote: >> On Nov 18, 2012, at 5:05 PM, David Blaikie <dblaikie at gmail.com> wrote: >>> TypeLoc

Chris Lattner wrote: >Could you try compiling and running this program: > >--- >#include <limits> >#include <iostream> >int main() { > std::cerr << std::numeric_limits<float>::infinity() << "\n"; >} >--- > > Sure thing. It prints "0". Calling that inifinity is somewhat of a stretch, isn't it ? What on earth

On Wed, 5 May 2004, Finn S Andersen wrote: > Chris Lattner wrote: > > >Could you try compiling and running this program: > > > >--- > >#include <limits> > >#include <iostream> > >int main() { > > std::cerr << std::numeric_limits<float>::infinity() << "\n"; > >} > >--- > > > > > Sure

Hi, I recently tried to follow the instructions on http://vmkit.llvm.org/get_started.html but all I get is -- snip -- In file included from /home/birdspider/vmkit-test/llvm/include/llvm/Support/SwapByteOrder.h:20: /usr/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.0/../../../../include/c++/4.7.0/limits:1404:27: error: use of undeclared identifier '__int128'; did you mean

On Thu, 6 May 2004, Alkis Evlogimenos wrote: > > But making the consequential changes in LLVM seems trickier. > > Do you plan to correct it in CVS, or is there a path I can follow > > to fix it myself on my own installation ? > > The easy way to do it in your area is to replace all occurences of > std::numeric_limits<float>::infinity() with HUGE_VAL. The only two

Hello. I'm new to this list, but I've been using Clang for a while (and C++ for many years). I've encountered a problem when compiling with -O1 on FreeBSD/amd64 11.1 (with bundled Clang, i.e. 4.0.0, as well as with 5.0.1 and 6.0.0 from ports). I asked on comp.lang.c++ and the code was also confirmed to misbehave on Linux, so they suggested I post it here. What follows is the

Chris Lattner wrote: >I think that we should switch to C constants in this case. Can you try >#include <math.h> and use HUGE_VAL instead? > It works: [finna at coplin11 ~/test]$ cat tst.cpp #include <limits> #include <iostream> #include <math.h> int main() { std::cerr << std::numeric_limits<float>::infinity() << "\n"; std::cerr

Hello all, The itanium demangler in libcxxabi (and also, llvm/lib/Demangle) is really slow. This is largely because the textual representation of the symbol that is being demangled is held in a std::string, and manipulations done during parsing are done on that string. The demangler is always concatenating strings and inserting into the middle of strings, which is terrible. The fact that the

On Thu, Nov 29, 2012 at 8:16 PM, Richard Smith <richard at metafoo.co.uk> wrote: > On Thu, Nov 29, 2012 at 7:43 PM, Eli Friedman <eli.friedman at gmail.com> > wrote: >> >> On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote: >> > Moving to LLVM dev to discuss the possibility of extending the cast >> > infrastructure to

On Mon, 2 May 2005, Jeff Cohen wrote: > The recently added code: > static Constant *Div(const ConstantClass *V1, const ConstantClass *V2) { > if (V2->isExactlyValue(0.0)) return ConstantClass::get(*Ty, INFINITY); > if (V2->isExactlyValue(-0.0)) return ConstantClass::get(*Ty, -INFINITY); > if (V2->isNullValue()) return 0; > BuiltinType R =

Yes, that will work. I'll make the change. Chris Lattner wrote: > On Mon, 2 May 2005, Jeff Cohen wrote: > >> The recently added code: >> static Constant *Div(const ConstantClass *V1, const ConstantClass *V2) { >> if (V2->isExactlyValue(0.0)) return ConstantClass::get(*Ty, INFINITY); >> if (V2->isExactlyValue(-0.0)) return ConstantClass::get(*Ty,