search for: sitvanit

In order to isolate the problem I am now running on a machine whose only installation of gcc/g++ is gcc44, g++44 For this installation I am getting the following error: COMPILE: clang_linux/asan-i386/i386: /gpfs/haifa-p4/00/pincette/sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc /.../sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:19:10: fatal error: 'new' file not found #include <new> ^ 1 error generated. make[5]: *** [/gpfs/haifa-p4/00/pincette/sitvanit/LLVM/build...

Ok, I got. You should install libstdc++44-devel, too. Please try to install gcc44-c++ and libstdc++44-devel. Note: gcc44-c++ depends on gcc44, but gcc44-c++ and libstdc++44-devel are independent each other, at least on my host, CentOS5. ...Takumi 2012/7/15 Sitvanit Ruah <RUAH at il.ibm.com>: > In order to isolate the problem I am now running on a machine whose only > installation of gcc/g++ is gcc44, g++44 > > For this installation I am getting the following error: > > > COMPILE: > clang_linux/asan-i386/i386: /gpfs/haifa-p4/00...

Hi Sitvanit, On 12/07/12 22:18, Sitvanit Ruah wrote: > I ran "configure -help " and it says > > usage: configure [OPTION]..... [VAR=VALUE] > > So I assume configure CC=... is the right syntax. Isn't it? while you might think so, try it the other way round. Also, by doing mak...

Hi Sitvanit, > I tried > > CC=gcc44 CXX=g++44 ../llvm/configure > > and got > > CC=gcc44: Command not found > > So the syntax is indeed as wriiten in the help. actually, no, this just means that you are using a shell that doesn't support this syntax. What shell are you using...

I tried CC=gcc44 CXX=g++44 ../llvm/configure and got CC=gcc44: Command not found So the syntax is indeed as wriiten in the help. Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory Tel: 972-4-828-1249 From: Duncan Sands <baldrick at free.fr> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: Konstantin Tokarev <annulen at yandex.ru>, llvmdev at cs.uiuc.edu, llvmdev-bounces at cs.uiuc.edu Date: 13...

...est level to use for backend development? We do not need to generate machine code, but rather an intermediate representation that will give us the control flow graph. Is this the llvm IR? If so, how do I read into memory a file that was generated by clang++ -emit-llvm <source file>. Thanks, Sitvanit Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory Tel: 972-4-828-1249 From: Konstantin Tokarev <annulen at yandex.ru> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: llvmdev at cs.uiuc.edu Date: 01/08/2012 01:22 PM Subject: Re:[LLVMdev] Reading the AST from the bitcode gen...

> Hi all, > After reading the documentation on clang I still have the following > question: > How do I read the bitcode generated by clang from a C++ file? I need to > have all the AST information in memory. AST has nothing to do with LLVM bitcode. -- Regards, Konstantin

PS: Do you actually have gcc-4.4 installed and in your path? What do the commands gcc44 -v and g++44 -v output? On 15/07/12 10:59, Duncan Sands wrote: > Hi Sitvanit, > >> I tried >> >> CC=gcc44 CXX=g++44 ../llvm/configure >> >> and got >> >> CC=gcc44: Command not found >> >> So the syntax is indeed as wriiten in the help. > > actually, no, this just means that you are using a shell that doesn...

...nux/4.1.2/../../../../include/c+ +/4.1.2/i386-redhat-linux/bits/gthr-default.h:117:1: error: weakref declaration must have internal linkage __gthrw(pthread_mutexattr_destroy) Could you guide me on how to resolve these errors? I downloaded the sources from the web page (not from SVN). Thanks, Sitvanit Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory

> Yes, it is the same error referring to 4.1.2. > > /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ > +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref > declaration must have internal > linkage > __gthrw(pthread_key_delete) > > There are several such errors. Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g++44

I ran "configure -help " and it says usage: configure [OPTION]..... [VAR=VALUE] So I assume configure CC=... is the right syntax. Isn't it? Regard, Sitvanit From: Konstantin Tokarev <annulen at yandex.ru> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: llvmdev-bounces at cs.uiuc.edu, llvmdev at cs.uiuc.edu, Duncan Sands <baldrick at free.fr> Date: 12/07/2012 05:09 PM Subject: Re:[LLVMdev] Compiling llvm and Clang on Linux...

It's undocumented FAQ, if you are using RHEL5 (or clone). - install gcc44-c++ - Build with CC=gcc44 CXX=g++44 - You may need "CC=clang -std=gnu89" to use clang with its glibc. Have fun! ps. AFAIK, clang can be built more easily on centos6. ...Takumi 2012/7/11 Sitvanit Ruah <RUAH at il.ibm.com>: > > Hello all, > I am new to this mailing list so I hope this is the right place to post the > following question. > > We are considering using Clang front end for our tool. I tried to compile > LLVM > (using configure followed by make from...

...ne line #include <algorithm> in llvm/projects/compiler-rt/lib/asan/asan_posix.cc the line is preceded by the comment // Should not add dependency on libstdc++ Below are the gcc44 directories installed on the machine. Do you know what else is needed in order to resolve the problem? Thanks, Sitvanit /usr/bin/gcc44 /usr/bin/gcov44 /usr/bin/i386-redhat-linux6E-gcc44 /usr/lib/gcc /usr/lib/gcc/i386-redhat-linux6E /usr/lib/gcc/i386-redhat-linux6E/4.4.6 /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbegin.o /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbeginS.o /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbegi...

...function 'round' conftest.c:165: warning: the use of `mktemp' is dangerous, better use `mkstemp' conftest.c:160: warning: conflicting types for built-in function 'strdup' configure:20847: WARNING: LLVM will be built thread-unsafe because atomic builtins are missing Thanks, Sitvanit Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory

Hi all, After reading the documentation on clang I still have the following question: How do I read the bitcode generated by clang from a C++ file? I need to have all the AST information in memory. Thanks, Sitvanit Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory Tel: 972-4-828-1249

Hi, > I ran > ../llvm/configure CC=gcc44 CXX=g++44 > make > > and still got the same error (I checked and CC=gcc44 and CXX=g++44 now in > build/Makefile.config).. is it exactly the same error? The original error referred to gcc-4.1 header files. Does the new error still refer to gcc-4.1 header files, or is it now talking about gcc-4.4 header files? Ciao, Duncan.