llvm-c++-api

问题 I want to link all LLVM libraries in my cmake C++ project. I use llvm-config --components to get all the components of LLVM, it gives me: $ llvm-config --components aarch64 aarch64asmparser aarch64codegen aarch64desc aarch64disassembler aarch64info aarch64utils aggressiveinstcombine all all-targets amdgpu amdgpuasmparser amdgpucodegen amdgpudesc amdgpudisassembler amdgpuinfo amdgpuutils analysis arm armasmparser armcodegen armdesc armdisassembler arminfo armutils asmparser asmprinter

问题 The man page for opt says: "It takes LLVM source files as input, runs the specified optimizations or analyses on it, and then outputs the optimized file or the analysis results". My Goal: To use the inbuilt optimisation pass -dce available in opt . This pass does Dead Code Elimination My Source file foo.c : int foo(void) { int a = 24; int b = 25; /* Assignment to dead variable -- dead code */ int c; c = a * 4; return c; } Here is what I did: 1. clang-7.0 -S -emit-llvm foo.c -o foo.ll 2. opt

问题 The man page for opt says: "It takes LLVM source files as input, runs the specified optimizations or analyses on it, and then outputs the optimized file or the analysis results". My Goal: To use the inbuilt optimisation pass -dce available in opt . This pass does Dead Code Elimination My Source file foo.c : int foo(void) { int a = 24; int b = 25; /* Assignment to dead variable -- dead code */ int c; c = a * 4; return c; } Here is what I did: 1. clang-7.0 -S -emit-llvm foo.c -o foo.ll 2. opt

问题 I have written a pass to detect and print the label of basicblocks in a function, for I want to use splitBasicBlock() further. I wrote that like this: virtual bool runOnModule(Module &M) { for(Module::iterator F = M.begin(), E = M.end(); F!= E; ++F) { errs()<<"Function:"<<F->getName()<<"\n"; //for(Function::iterator BB = F->begin(), E = F->end(); BB != E; ++BB) for (iplist<BasicBlock>::iterator iter = F->getBasicBlockList().begin(); iter != F->getBasicBlockList().end(); iter++) { BasicBlock*

问题 I have written a pass to detect and print the label of basicblocks in a function, for I want to use splitBasicBlock() further. I wrote that like this: virtual bool runOnModule(Module &M) { for(Module::iterator F = M.begin(), E = M.end(); F!= E; ++F) { errs()<<"Function:"<<F->getName()<<"\n"; //for(Function::iterator BB = F->begin(), E = F->end(); BB != E; ++BB) for (iplist<BasicBlock>::iterator iter = F->getBasicBlockList().begin(); iter != F->getBasicBlockList().end(); iter++) { BasicBlock*

问题 I found it hard to understand the LLVM C++ API. Is there any relationship between LLVM C++ API and LLVM IR? Also, how could one use the LLVM C++ API? 回答1: To (greatly) simplify, LLVM is a C++ library for writing compilers. Its C++ API is the external interface users of the library employ to implement their compiler. There's a degree of symmetry between LLVM IR and part of the LLVM C++ API - the part used to build IR. A very good resource for getting a feel for this symmetry is http://llvm.org

问题 I found it hard to understand the LLVM C++ API. Is there any relationship between LLVM C++ API and LLVM IR? Also, how could one use the LLVM C++ API? 回答1: To (greatly) simplify, LLVM is a C++ library for writing compilers. Its C++ API is the external interface users of the library employ to implement their compiler. There's a degree of symmetry between LLVM IR and part of the LLVM C++ API - the part used to build IR. A very good resource for getting a feel for this symmetry is http://llvm.org

问题 I found it hard to understand the LLVM C++ API. Is there any relationship between LLVM C++ API and LLVM IR? Also, how could one use the LLVM C++ API? 回答1: To (greatly) simplify, LLVM is a C++ library for writing compilers. Its C++ API is the external interface users of the library employ to implement their compiler. There's a degree of symmetry between LLVM IR and part of the LLVM C++ API - the part used to build IR. A very good resource for getting a feel for this symmetry is http://llvm.org

问题 The LLVM project does not distinguish between signed and unsigned integers as described here. There are situations where you need to know if a particular variable should be interpreted as signed or as unsigned though, for instance when it is size extended or when it is used in a division. My solution to this is to keep a separate type information for every variable that describes whether it is an integer or a cardinal type. However, I am wondering, isn't there a way to "attribute" a type in

问题 The LLVM project does not distinguish between signed and unsigned integers as described here. There are situations where you need to know if a particular variable should be interpreted as signed or as unsigned though, for instance when it is size extended or when it is used in a division. My solution to this is to keep a separate type information for every variable that describes whether it is an integer or a cardinal type. However, I am wondering, isn't there a way to "attribute" a type in