similar to: [LLVMdev] tutorial

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] tutorial"

2010 Apr 27
1
[LLVMdev] llvm-2.7: --with-udis86 failure
Debug build on x86_64 with`--with-udis86=<path>' option to 'configure' seems broken. Configure command line: ./configure --disable-optimized --enable-assertions --enable-debug-runtime --enable-debug-symbols --enable-jit --enable-pic --enable-targets=x86_64 --with-udis86=/somepath/udis86/udis86-1.7 At least 2 issues: (1) '-L/somepath/udis86/udis86-1.7' is added to the
2010 Jun 30
0
[LLVMdev] vmkit build problems
Hi again Nicolas, Can you please tell me the output of your llvm-gcc -v and llvm-config -version? Mine is below, perhaps its because I built llvm with enable-jit? Do you have users of vmkit? ie has anyone other than the llvm team been successful at building and running vmkit? I tried on a core2 machine (albeit also karmic) and have the same problem. Can you build a fresh machine (virtual
2010 Jun 30
2
[LLVMdev] vmkit build problems
Hi Zoe, Unfortunately, I don't have access to a x64 machine anymore, so I can't test that architecture on vmkit. Could you install a virtual machine on your machine that is x86_32? I know it has been successfully built and ran on x86_32 on different systems. Cheers, Nicolas On Wed, Jun 30, 2010 at 7:49 AM, Zoe Wolk <zoewolk at gmail.com> wrote: > Hi again Nicolas, > >
2007 Aug 10
2
jinfo, jboss and ExtendedDTraceProbes
Hi, I would like to use dtrace to observe some behaviour in my J2EE app running in JBoss. I start JBoss normally in a 1.6 VM. When I try to enable set the ExtendedDTraceProbes flag using jinfo, I get a thread dump in the JBoss console and the message: "Unable to open door: target process not responding or HotSpot VM not loaded" in the jinfo console. I have tried this with both
2014 Jun 11
1
Recent (6.02) PXELINUX on Soekris net4501
* Ady, 2014-06-11 : > Perhaps it would be worth testing with official pre-built binaries of > Syslinux 6.03-pre14 using the following config: Different behaviour. * pxelinux.0: After TFTP load of pxelinus.0, spits out gibberish for ~1 minute (as though it had set an incorrect default serial port speed), then loads config and switches back to correct baud rate. "Hello
2010 Jul 05
0
[LLVMdev] vmkit build problems
Hi Zoe, maybe you've already solved your problem with VMKit configuration, but here you can find a mini-tutorial that I've done to guide people on VMKit installation. http://www2.dcc.ufmg.br/laboratorios/llp/wiki/doku.php?id=afpf Best regards, Alysson On Wed, Jun 30, 2010 at 1:34 PM, nicolas geoffray < nicolas.geoffray at gmail.com> wrote: > Hi Zoe, > > Unfortunately, I
2007 Nov 09
1
[LLVMdev] Newbie JITter
Thanks Evan. On 09/11/2007, at 6:50 PM, Evan Cheng wrote: >> 1. What optimization passes, if any, should I run on the module >> before I pass it to the ExecutionEngine. > > The default JIt driver, lli, runs everything. My reading of the lli source indicates that it's not explicitly doing any opt passes - is that happening implicitly in the ExecutionEngine? I can see
2012 May 07
2
how to deduplicate records, e.g. using melt() and cast()
Esteemed UseRs, This must be embarrassingly trivial to achieve with e.g., melt() and cast(): deduplicating records ("pw.X" in example) for a given set of responses ("cond.Y" in example). Hopefully the runnable example shows clearly what i have and what i'm trying to convert it to. But i'm just not getting it, ?cast that is! So i'd really appreciate some ones
2018 Sep 26
2
OptBisect implementation for new pass manager
Philip, It kinda depends on user expectations. What do you really expect as a result of your compilation when you set -opt-bisect-limit=X? Do you just get a resulting IR and scan for the bad pattern? Then you dont care about pass sequences and do brute-force bisect. Do you expect to get a runnable code at the end and check for buggy run-time behavior? Then you need to keep the passes that are
2009 Mar 27
2
[LLVMdev] Connecting JITted code to gdb
On Fri, Mar 27, 2009 at 3:48 PM, Evan Cheng <evan.cheng at apple.com> wrote: > Run with -debug-only=jit. OT: I take it the recommended model for tools that embed LLVM is for them to accept all of LLVM's command line arguments on their own command lines? For Python, it'd be much nicer to make this stuff tweakable through a module at runtime, or even, for thread-safety reasons, as
2010 Aug 01
3
xm list vs. xl list: more differences?
I see that "xl list" shows a domain waiting idly for console input as "r", whereas "xm list" shows the same domain as "b". I also see that the State field for "xl list" contains only three characters (e.g. "r--"), whereas "xm list" shows six (e.g. "-b----"). Is this expected/intended (e.g. "r" in xm list
2010 Jun 30
1
[LLVMdev] vmkit build problems
Hi Nicolas, No, I built llvm-gcc myself by checking it out via svn, using these instructions: http://llvm.org/docs/GCCFEBuildInstrs.html thanks -Z > Hi Zoe > (Please, try to reply to the same thread) > I think you may have an old version of llvm-gcc. Did you compile > llvm-gcc yourself? The provided llvm-gcc binary for llvm 2.7 is > too old for vmkit. > > Nicolas >
2008 Mar 10
3
format a number
Hi there! I have i.e. v = c(0.43554, -0.22343), and so on. Now I'd like to make a format like format(v, digits=2) but without the leading 0, so 0.43554 becomes .44, -0.22343 becomes -.22 How can I do that? runnable example for copy and paste: v = c(0.43554, -0.22343) format(v, digits=2) Thanks, Martin -- Ihr Partner f?r Webdesign, Webapplikationen und Webspace.
2007 Nov 08
3
[LLVMdev] Newbie JITter
Hi, I'm experimenting with using LLVM to generate dynamic FFI bridges in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from dynamically generated assembler source to machine code, and I have that all working, copied from the llc tool and the JIT example. I have two questions: 1. What optimization passes, if any, should I run on the module before I pass it to the
2010 Feb 23
2
Freezing Rails in ovirt-server...
The ovirt-server package has started to slip behind the curve WRT Ruby on Rails development; i.e., the current version of ovirt-server is not quite runnable as is on F12. And with F13 coming, the gap's only going to widen. So I'm considering the idea of freezing the version of Rails on the ovirt-server project for the time being. I'll check with the Fedora packaging team to see if
2014 Feb 27
3
[PATCH RFC v5 7/8] pvqspinlock, x86: Add qspinlock para-virtualization support
On 27/02/14 13:11, Paolo Bonzini wrote: > Il 27/02/2014 13:11, David Vrabel ha scritto: >>> > This patch adds para-virtualization support to the queue spinlock code >>> > by enabling the queue head to kick the lock holder CPU, if known, >>> > in when the lock isn't released for a certain amount of time. It >>> > also enables the mutual
2014 Feb 27
3
[PATCH RFC v5 7/8] pvqspinlock, x86: Add qspinlock para-virtualization support
On 27/02/14 13:11, Paolo Bonzini wrote: > Il 27/02/2014 13:11, David Vrabel ha scritto: >>> > This patch adds para-virtualization support to the queue spinlock code >>> > by enabling the queue head to kick the lock holder CPU, if known, >>> > in when the lock isn't released for a certain amount of time. It >>> > also enables the mutual
2014 Feb 27
3
[PATCH RFC v5 7/8] pvqspinlock, x86: Add qspinlock para-virtualization support
On 02/27/2014 08:15 PM, Paolo Bonzini wrote: [...] >> But neither of the VCPUs being kicked here are halted -- they're either >> running or runnable (descheduled by the hypervisor). > > /me actually looks at Waiman's code... > > Right, this is really different from pvticketlocks, where the *unlock* > primitive wakes up a sleeping VCPU. It is more similar to PLE
2014 Feb 27
3
[PATCH RFC v5 7/8] pvqspinlock, x86: Add qspinlock para-virtualization support
On 02/27/2014 08:15 PM, Paolo Bonzini wrote: [...] >> But neither of the VCPUs being kicked here are halted -- they're either >> running or runnable (descheduled by the hypervisor). > > /me actually looks at Waiman's code... > > Right, this is really different from pvticketlocks, where the *unlock* > primitive wakes up a sleeping VCPU. It is more similar to PLE
2009 Mar 27
0
[LLVMdev] Connecting JITted code to gdb
On Fri, Mar 27, 2009 at 2:25 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Fri, Mar 27, 2009 at 3:48 PM, Evan Cheng <evan.cheng at apple.com> wrote: >> Run with -debug-only=jit. > > OT: I take it the recommended model for tools that embed LLVM is for > them to accept all of LLVM's command line arguments on their own > command lines? Well, sort of...