similar to: [LLVMdev] llc unhandled attribute

>> > I was trying to do a source to source transformation in llvm from c++11 >> > more >> > basic c++ (to transform away auto etc.) using llvm3.1. >> > I generate llvm bitcode using "clang++ -emit-llvm ...", but executing >> > llc >> > -march=cpp throws >> > /home/broes/software/llvm/lib/Target/CppBackend/CPPBackend.cpp:493:

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

+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; };"

vmkit fails to build because llvm-as with llc -march=cpp generate wrong code for AttrListPtr AttrListPtr::get(ArrayRef< AttributeWithIndex >Attrs) http://llvm.org/doxygen/classllvm_1_1AttrListPtr.html#a3a19622d131e9f0d981398f54cf6acfc bellow you can see the faulty generated code llvm-as ./vmkit/lib/vmkit/Compiler/LLVMRuntime.ll -o - | llc -march=cpp -cppgen=contents -o - | grep

Yest. thanks. I just resolved this error by installing MPFR, MPC and GMP(by the way, these are not listed as prerequisites in the website.). But other errors come: /home/xxx/llvm/tools/dragonegg/src/TypeConversion.cpp: In function > ‘llvm::FunctionType* ConvertArgListToFnType(tree_node*, > llvm::ArrayRef<tree_node*>, tree_node*, bool, llvm::CallingConv::ID&, >

>> /usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/plugin/include/real.h:27:18: >> fatal error: mpfr.h: No such file or directory > > I did some search but found few relevant results. > Any idea what's going on? Do you have MPFR installed? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi, When I tried to compile Dragonegg using the SVN trunk code, I encountered failure with error message: In file included from > /usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/plugin/include/rtl.h:28:0, > from /home/xxx/llvm/dragonegg/src/Convert.cpp:63: > /usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/plugin/include/real.h:27:18: > fatal error: mpfr.h: No such

Hi Guys, I am using the Postdom pass and I would like to get the root of the tree. However, everytime I try to get the root, I get a segfault. I don't know why the environment can't find DominatorTreeBase. Below is the code that generates the Segfault. In my .h file I include Dominators.h PDT.getRootNode(); //PDT is a reference to a PostDominatorTree dyld: lazy symbol binding

Hi All, I was checking for GIT or SVN versions corresponding to llvm3.1 release by checking svn and git logs, but failed to find the exact match. I checked with r156747, which is the last version it shows in      http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/ but when I 'diff' this with the 'downloaded llvm3.1 release'(http://llvm.org/releases/download.html#3.1), then I

Hi Team, I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1. The code snippet looks like the following: Constant *func; void add( Module *M) { func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL); } virtual bool runOnModule(Module &M) { add (&M); for(Module::iterator F = M.begin(), E = M.end(); F !=

Hi Ahmad, On 03/01/13 16:26, Hassan, Ahmad wrote: > Hi Team, > > I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1. > The code snippet looks like the following: > > Constant *func; > > void add( Module *M) { > > func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL); this function has no

I'm seeing a build failure... In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/ Attributes.cpp:14: /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member function 'llvm::Attributes llvm::AttrListPtr::getParamAttributes(unsigned int) const': /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h:152: error: 'assert' was not declared in this scope

Won't it be http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/final/ On Tue, Jan 8, 2013 at 7:46 PM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > I was checking for GIT or SVN versions corresponding to llvm3.1 release by > checking svn and git logs, but failed to find the exact match. > > I checked with r156747, which is the last version it shows

On Wed, May 4, 2016 at 3:10 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > As in "look at the source of clang" or as in "look at the -S -emit-llvm" > output? If you mean the former, then would that be easy for someone who > hasn't seen the clang source before? > Generally the latter - then potentially set some breakpoints & look at

Hello, I was trying to compile a simple program with the CppBackend like so: $ clang str_arg.c -emit-llvm -S $ llc -march=cpp str_arg.ll It produces a file `str_arg.cpp` as expected, however it doesn't seem that the resulting file is correct. For once, it includes `<llvm/Analysis/Verifier.h>` which seems to have been moved to `llvm/IR/Verifier.h` as far back as 2013. My question is

That is what I don't understand. This symbol is defined in Dominators.h, which I include in my file. I don't understand why I am getting this error. Here is my opt command, "opt -load LLVMMyDomPass.dylib -mdp < test.bc > test.d.bc" George On Tue, Aug 21, 2012 at 3:25 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi George, > > ... > > dyld: lazy

The usual advice I provide people is "see what Clang does with an equivalent C construct" On Wed, May 4, 2016 at 12:18 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > Hi, > > There is another benefit to keeping the CppBackend: it's great for > learning how to use the IR and the C++ API in particular, as can be seen > from this SO Q&A: >

I was just fixing a bug that was caused by `stdout` being closed before the runtime has done `fflush(stdout)` [or however this is implemented in the runtime]. The cause of this seems to be that `outs()` returns a static object created from `raw_fd_stream(STDOUT_FILENO, true)` - the `true` being the `shouldClose` parameter. Surely LLVM is not supposed to close `stdout` as part of its operations?

+1 On Wed, May 4, 2016 at 3:10 AM, Filipe Cabecinhas via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > On Wed, May 4, 2016 at 9:35 AM, Ronan KERYELL via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >>>>>> On Tue, 3 May 2016 16:36:01 -0400, Rafael Espíndola via llvm-dev < > llvm-dev at lists.llvm.org> said: > > > >

We've had this argument before. IMO LLVM should not be in the business of closing stdout, and no code in lib/ should print to stdout because users may expect output there (-o -). On Fri, Jan 23, 2015 at 10:20 AM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2015-Jan-23, at 09:52, mats petersson <mats at planetcatfish.com> wrote: > > > >