similar to: [LLVMdev] llc -march=cpp is broken?

In r134967 it still worked, and in r137742 it now doesn't. I used such flags: --enable-assertions --enable-shared --enable-libffi --enable-debug-runtime --enable-debug-symbols --disable-optimized Before build would create directory tools/llvm-shlib under the build tree. Now it is missing. Yuri

On 10/02/2012 13:01, Duncan Sands wrote: > > I think Chris is the right person to look at this, hopefully he will. Now 5 months passed. I updated the patch for this current revision. Can anybody review this and check in please? http://llvm.org/bugs/show_bug.cgi?id=13163 Yuri

This function (understandably) takes quite a long time, because it has to go through each function in module and write its binary. But it probably can be parallelized if different threads would write binaries separately, and then merge them together. Is this implemented or planned? Yuri

On 02/02/2014 01:48, David Chisnall wrote: > In most calling conventions, this is a callee-save register. After its last use, the register allocator may reuse that register. On x86 and ARM, the register that contains this is also (usually) the register used for But the rule "after the last use, the register allocator may reuse it" is also introduced by llvm, since register

How can I copy the value from another BB? PHI instruction with one argument would fit, but it requires that all arguments are in immediately preceding BBs. Yuri

I did these steps: * checked out llvm trunk, and clang trunk * created symbolic link llvm/tools/clang * created separate folder: llvm-objects * run configure and gmake in llvm-objects It builds ok until it hits clang, at which point I get an this error: gmake[2]: Entering directory `/tmp/llvm-svn/llvm-objects/tools/clang' Makefile:44: Makefile.config: No such file or directory Makefile:127:

Yuri, on which host? 2011/8/17 Yuri <yuri at rawbw.com>: > In r134967 it still worked, and in r137742 it now doesn't. > I used such flags: --enable-assertions --enable-shared --enable-libffi > --enable-debug-runtime --enable-debug-symbols --disable-optimized > > Before build would create directory tools/llvm-shlib under the build > tree. Now it is missing. In my

On Apr 17, 2013, at 7:26 PM, Yuri <yuri at rawbw.com> wrote: > On 10/02/2012 13:01, Duncan Sands wrote: >> >> I think Chris is the right person to look at this, hopefully he will. > > Now 5 months passed. I updated the patch for this current revision. > Can anybody review this and check in please? > > http://llvm.org/bugs/show_bug.cgi?id=13163 >

I think my patch fell through the cracks: http://llvm.org/bugs/show_bug.cgi?id=13163 Could anybody please check it in? Thanks, Yuri

I've built clang+llvm in an object directory successfully, and I'm sure others have. I'd guess the problem is the symlink, so I'd give it a shot without it. Reid On Thu, Jun 10, 2010 at 7:43 AM, Diego Iastrubni <diegoiast at gmail.com> wrote: > can you tell what commands exactly did you use? > > What I usually do is: > > svn co llvm... > mkdir

On 02/19/2011 14:52, Yuri wrote: > Will MC path for JNI be included in 2.9? > Sorry. I meant: Will MC path for JIT be included in 2.9?

I get a crash when I try to link multiple modules registered in their individual contexts. Documentation for Linker::LinkModules doesn't mention anything about contexts, and the first link succeeds. But the second link crashes. Is this not the right way to merge such modules? If not, then what is the right way? In any case, documentation for Linker::LinkModules should say if contexts are

On Feb 19, 2011, at 8:05 PM, Yuri wrote: > On 02/19/2011 14:52, Yuri wrote: >> Will MC path for JNI be included in 2.9? >> > > Sorry. I meant: Will MC path for JIT be included in 2.9? While it would be nice, it doesn't seem like anyone is working on it at the moment. -Chris

can you tell what commands exactly did you use? What I usually do is: svn co llvm... mkdir llvm/tools/clang svn co llvm/tools/clang mkdir cmake-build cd cmake-build cmake ../ make Try something similar by running "../configure", it should work. On Thu, Jun 10, 2010 at 11:23 AM, Yuri <yuri at rawbw.com> wrote: > I did these steps: > * checked out llvm trunk, and clang

----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: Yuri <yuri at rawbw.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sun, February 20, 2011 3:26:35 AM > Subject: Re: [LLVMdev] Announcing: LLVM 2.9 Tentative Release Schedule > > > On Feb 19, 2011, at 8:05 PM, Yuri wrote: > > > On 02/19/2011 14:52, Yuri wrote: > >>

Have you found http://llvm.org/docs/DebuggingJITedCode.html? The JIT already has support for something like this for gdb's benefit. Perftools and valgrind just don't know how to find it yet. On Sat, Jun 19, 2010 at 2:03 PM, Yuri <yuri at rawbw.com> wrote: > This new option (--jit-emit-debug-function-range) will allow to output > function information for memory ranges that

When I try running simple example with exceptions through JIT I get this output: terminate called after throwing an instance of 'E*' Why exceptions don't work in JIT and what it takes to make them work? Yuri --- e.C --- #include <stdio.h> #include <stdlib.h> class E { }; void xmain() { try { throw new E; } catch (E *e) { printf("caught!\n");

Every value used in .ll file normally has '#uses=' printed next to it. But functions don't have this. Is there a way to make llvm to print uses of functions within the current module? Thank you, Yuri

I have C++ project that builds fine with g++. But when I try to replace g++ with clang++ I get such errors (see below) during link. What might be a problem? Yuri --- errors are like this --- local symbol 1: discarded in section `.text.SomeSymbolHere1' local symbol 2: discarded in section `.text.SomeSymbolHere2' ... ...

I noticed that this command returns NO through ssh: > $ ssh user at host "if [ -t 1 ]; then echo YES; else echo NO; fi" > NO and YES when run locally (of course): > $ if [ -t 1 ]; then echo YES; else echo NO; fi > YES I can't find any command line option related to running command remotely in terminal. I think users intuitively expect commands to be run in