similar to: [LLVMdev] Reading the AST from the bitcode generated by clang

What is the best 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:

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,

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? Try export CC=gcc44 export CXX=g++44 ../llvm/configure Ciao, Duncan. >

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

Thanks for the information. I am running on a machine on which gcc44 is installed but whose default installation is 4.1.2. 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).. I tried also ../llvm/configure CC=gcc44 CXX=g++44 --include_dir=<gcc44 include dir> but it didn't help

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:

> 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

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 make VERBOSE=1 you can see which compiler is really being used. Ciao, Duncan. > >

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

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 the llvm top directory) on LINUX X86 with gcc 4.1.2. I got several compilation error messages of the form /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+

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:

Hi all, I ran ../llvm/configure CC=g44 CXX=g++44 and the exit code was 0, but in config.log I found errors (mostly about missing files) and warnings (mostly about conflicts in builtin functions). I thought maybe the fact I later get compilation errors when running make is related to these. How do I correct these errors? or can they be ignored? The full list of errors from config.log is

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. >

> 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

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.

Hi, I am new to LLVM, so I am sorry if the question I am going to ask has already been raised before. I will be thankful if anyone can describe me a quick way to search relevant topics within the list archive, When I am trying to compile a simple code, containing access to std::string, with clang: #include <string> int main() { std::string s; return

[we apologize if you receive multiple copies of this announcement] The Storage and Systems Department at IBM''s Haifa Research Lab (HRL), in collaboration with the Technion - Israel Institute of Technology, cordially invite you to a full-day workshop on the subject of virtualization within the SYSTOR 2007 conference. SYSTOR 2007 is the first high-quality refereed systems and storage

[we apologize if you receive multiple copies of this announcement] The Storage and Systems Department at IBM''s Haifa Research Lab (HRL), in collaboration with the Technion - Israel Institute of Technology, cordially invite you to a full-day workshop on the subject of virtualization within the SYSTOR 2007 conference. SYSTOR 2007 is the first high-quality refereed systems and storage

Hello, I am trying to use Clang to generate AST for C code in a different format. This format is specific to the term rewriting system that we use for source-to-source transformations. Studying the ast generated by Clang using the "-ast-print" option to the clang-cc, I see that the pre-processor expands the code(expected). Is there a way to get around and not print all the information

Hi, using the current version from the repository on Debug+Asserts mode I was able to generate Clangs AST on Gnu gv, however I noticed the tree provides no annotation to which part each statement it is referring to. For example, when it says binary operator I would like to know to which binary operator is it referring to. Is this possible with clang? I am using the ast-view option from cc1. As