similar to: [LLVMdev] Proposal for Adding MetaData to a BasicBlock

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

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

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

Hi, I am using visual studio 2008's generated solution file for clang/llvm. I was looking at the online demo where it gives out llvm2cpp program along with the llvm IR of the C code. I could not find any executable in the /bin directory for llvm2cpp. I was wondering if there is either source or executable of the llvm2cpp program that is used by llvm demo available for either llvm-2.7

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

> 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

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

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>

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

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>

Dear llvm-ers, I am trying to attach a customized metadata to llvm instructions. Let's say, I want to attach some number to each instruction. I am trying to use void Instruction::setMetadata(unsigned KindID, MDNode* Node) but I am not sure how to create a brand new instance of an MDNode. Do you have any code samples demonstrating how to do that? Due to some tool dependencies, I am using

> Dear llvm-ers, > I am trying to attach a customized metadata to llvm instructions. > Let's say, I want to attach some number to each instruction. > I am trying to use > > void Instruction::setMetadata(unsigned KindID, MDNode* Node) > > but I am not sure how to create a brand new instance of an MDNode. > Do you have any code samples demonstrating how to do that?

Hello, Thank you very much for the pointers. I am are able to create new MDNodes, filled with some constants, and attach them to llvm instructions. However, the metadata map is not getting updated as expected. For example, instead of the expected new entry !n = metadata !{some values} we are getting !n = metadata !{null} Do you know what might be wrong? Do we need to enter the MDNodes into the

On 12/21/11 11:24 PM, Oksana Tkachuk wrote: > Hello, > Thank you very much for the pointers. > I am are able to create new MDNodes, filled with some constants, and > attach them > to llvm instructions. However, the metadata map is not getting updated > as expected. > For example, instead of the expected new entry If you look at PoolMDPass::runOnModule(), you'll see that

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

> On 2015 Apr 14, at 21:46, David Blaikie <dblaikie at gmail.com> wrote: > > On Tue, Apr 14, 2015 at 9:33 PM, Duncan P. N. Exon Smith > <dexonsmith at apple.com> wrote: >> >> `Function` definitions should support `MDNode` attachments, with a >> similar syntax to instructions: >> >> define void @foo() nounwind !attach !0 { >>

Hi, I want to remove metadata from an instruction. Is there any way doing this in my pass? Regards, Kyriakos -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130815/08200e23/attachment.html>