similar to: [LLVMdev] llvm2cpp executable

Hi ! The Hello world pass sources are in llvm/lib/Transform/Hello/* If you compile llvm, the Hello library will be compiled too. It's not installed but it's in build_directory/Debug/lib/LLVMHello.so (or in build_directory/Release/lib/LLVMHello.so) Olivier. On Sun, Apr 18, 2010 at 7:35 AM, kalyan ponnala <ponnala.kalyan at gmail.com>wrote: > Hello, > > I was going

Hello, I was going through the LLVM docs "writing an LLVM Pass". Can someone tell me how to create the Hello.so file as it is said in the document. It talks about compiling the Hello pass using gmake. I am a Windows user (windows 7, cmake, visual studio 9 2008). I cant use cmake here as this hello pass has links to the llvm's solution file, I mean It uses some of the header files

Hi, I am trying to understand LLVM. Can an expert tell me how to compare the kaleidoscope implementation with the LLVM's compiler implementation. I mean can anyone tell me about the lexer, parser, codegen related .cpp and .h files inside the LLVM solution project. I would like to understand the LLVM's compiler in the same way that the kaleidoscope compiler is explained. Thanks a lot.

Hi, I went through the front end part of the clang (a bit atleast) and I went through some of the documentation on the llvm.org website and was trying to know what happens after the front end is done with the code. Could you tell me how does llvm comes into picture as soon as clang part of the interface deals with the source code. Thanks. On Tue, Mar 16, 2010 at 12:55 AM, Bill Wendling

Thanks a lot for the reply guys. So, does that mean that I cant write my own passes if I work on Windows side of the LLVM? Is there any other way to use a new pass. How are windows users supposed to work? Thanks again. On Sun, Apr 18, 2010 at 7:16 AM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > > If you compile llvm, the Hello library will be compiled too. It's

Thanks duncan and samuel. I guess the optimization about striping dead prototypes was not working because of "no dead prototypes" to strip. The -std-compile-opts option works. I can see a change. And @samuel, I tried the clang's -o0 optimization level compiling, but I could not find any difference with or without that switch in the bitcode file generated. I used this command: clang

On Mar 15, 2010, at 8:15 PM, kalyan ponnala wrote: > Hi, > > I am trying to understand LLVM. Can an expert tell me how to compare the kaleidoscope implementation with the LLVM's compiler implementation. I mean can anyone tell me about the lexer, parser, codegen related .cpp and .h files inside the LLVM solution project. I would like to understand the LLVM's compiler in the same

Hi, I would like to know if the command llc -march=c hello.bc generates a c99 file or not. Is the cbackend target meant to be c99 or normal C. -- Kalyan Ponnala phone: 8163772059 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100219/e67c7a73/attachment.html>

Hello group, Per my posting on the Clang Newsgroup. I'm interested in doing some loop optimizations, towards this end I would like to add some custom Metadata to a Loop header. Loops in LLVM are represented using BasicBlocks, but unfortunately you can NOT add MetaData to a BasicBlock. Although you can add Metadata to an instruction. So I'm proposing to add the Metadata manipulation

Hello, I am trying to build llvm/clang using cmake and visual studio 2008 on windows vista. I want to convert the llvm bitcode file hello.bc into C code. I saw in the documentation that "llc -march=c hello.bc" would convert the bitcode and generate a c code file. but it says llc:error: invalid target "c" could you tell me why is it not working. and what is the way to convert

Hi, Could someone tell me how does a part of the source code get translated into metadata in the LLVM IR. and what kind of code gets parsed into metadata. Thanks -- Kalyan Ponnala phone: 8163772059 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100320/cd883472/attachment.html>

Hello Kalyan, There is one more thing you should know: Clang has maximum optimization turned on by default. You need to specify -O0 to turn it off if you want to see what opt does without clang running all of the optimizations first. --Sam ----- Original Message ---- > From: Duncan Sands <baldrick at free.fr> > To: llvmdev at cs.uiuc.edu > Sent: Sat, April 17, 2010 2:00:00 AM

> If you compile llvm, the Hello library will be compiled too. It's not > installed but it's in build_directory/Debug/lib/LLVMHello.so (or in > build_directory/Release/lib/LLVMHello.so) Loadable passes are not supported on windows due to lack of OS dynamic linking support (and I doubt they will be supported ever). -- With best regards, Anton Korobeynikov Faculty of Mathematics

Hello, I am trying to understand the opt tool. I wrote a program and created the .bc file using clang. And I used this .bc file to generate another .bc file using the opt tool. I dis-assembled this bitcode file and compared the output with previous unoptimized bitcode file. It was the same. I am not sure how to check the difference. Can anyone tell me if this is how we check the optimized output

After compiling llvm and the cfrontend, I tried to run llvm2cpp on a few of the .ll files in the test/Regression directory. When I try this, I get the following error: llvm2cpp: Invalid bytecode signature: 5552203B (Vers=0,Pos=4) Any help would be appreciated. thanks, Todd

On Sun, Feb 14, 2010 at 3:52 PM, kalyan ponnala <ponnala.kalyan at gmail.com>wrote: > I used cmake gui to build the clang/llvm solution file. > llc hello.bc -march=x86 -o hello.s > this above command works. But the c backend thing does not work in place of > x86. > The targets that the llc -version gave me are > x86 -32bit > x86 - 64bit > and the target triple is

Hi, According to the LLVM 2.6 Release Notes, it states: "LLVM now has experimental support for embedded metadata in LLVM IR, though the implementation is not guaranteed to be final and the .bc file format may change in future releases." Can someone please comment on it's status? Thanks, -- Kalyan Ponnala phone: 8163772059 -------------- next part -------------- An HTML

+Bill who worked on the attribute change On Mon, Mar 25, 2013 at 9:15 AM, Harris BAKIRAS <h.bakiras at gmail.com> wrote: > Hi everyone, > > We are using the llvm2cpp feature of LLVM in the VMKit project and there are > some issues that I would like to point out. > > I made a tiny reproducible example here, to be clear: > > echo "int main() { return 0; };"

Hi everyone, We are using the llvm2cpp feature of LLVM in the VMKit project and there are some issues that I would like to point out. I made a tiny reproducible example here, to be clear: echo "int main() { return 0; };" > test.c && clang test.c -emit-llvm -c -o - | llc -march=cpp -cppgen=function -cppfor=main -o - This command is supposed to generate the C++ code to

Okay, let me reiterate. The llvm2cpp option is *already* on the demo script page. If you choose that option, you just get an error message because llvm2cpp can't be found. Its harmless and everything else still works. I won't change the script for a couple of weeks, per Tanya's and your request. Reid. On Thu, 2006-08-10 at 10:48 -0700, Chris Lattner wrote: > On Thu, 10 Aug