search for: grokked

1. I have used gdata::read.xls() with much happiness. But every now and then it breaks. I have not, as yet, been able to construct a mental model about the class of .xls files for which it works. Does someone have a simple rule for predicting the circumstances under which it will work? 2. Just like there is a read.xls(), it'd be great if we have a read.ods() which directly

Hi, Is there a way for me to collect statistics about the number of loads/stores added by the "linearscan" register allocator (just like can be done with the "local" allocator)? I still haven't grokked very well the interaction between RALinScan and Spiller... Should I add those two statistics to the spiller's class? Thanks, -- Silvio Ricardo Cordeiro -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100...

Hi folks, I''m working on building up a puppet infrastructure, and I''m having the darndest time putting it all together. I''ve read through as many of the docs as I can find. I''ve read the best practices guide. And I''m still not grokking how to do what I want to do in puppet. I''ve spend enough time with cfengine that I''m sure

On Thu, Sep 26, 2013 at 12:22 PM, Preston Briggs <preston.briggs at gmail.com>wrote: > I think y'all underestimate how important documentation can be. > I'm a strong proponent for good documentation, and whenever I get a solid understanding of a specific part of LLVM I will usually write documentation for it. (I'm pretty clueless about backend stuff, which is why I

...On Aug 15, 2010, at 5:12 PM, Silvio Ricardo Cordeiro wrote: > > > Is there a way for me to collect statistics about the number of > loads/stores added by the "linearscan" register allocator (just like can be > done with the "local" allocator)? I still haven't grokked very well the > interaction between RALinScan and Spiller... Should I add those two > statistics to the spiller's class? > > RALinearScan asks the Spiller to spill a virtual register. The > StandardSpiller passes the request to LiveIntervals::addIntervalsForSpills. > Here, the...

Hey, I am Swapnil Raj I am student in Trinity College Dublin and I am interested in working on LLVM. I am really interested in two projects listed, the first one is the extending the clang AST with template information and the second is finding smart null pointer dereferences. I am passionate about compilers and interpreters, I have written a few small language based on lambda calculus. I am

with today's CVS commit (for those who stay up to date with the latest developments), you'll have to modify your Wine configuration to reflect the changes. First of all, your Wine configuration file now needs a WinMM section containing the following: [WinMM] "Drivers" = "wineoss.drv" "WaveMapper" = "msacm.drv" "MidiMapper" =

...t; > On Aug 15, 2010, at 5:12 PM, Silvio Ricardo Cordeiro wrote: > > > Is there a way for me to collect statistics about the number of loads/stores added by the "linearscan" register allocator (just like can be done with the "local" allocator)? I still haven't grokked very well the interaction between RALinScan and Spiller... Should I add those two statistics to the spiller's class? hmm, having information if an operation is (a, or part of a) spill generated by the register allocation would be benefical in some cases; Those memory operations cannon alias wi...

I'm having trouble grokking complex NaN's. This first set examples using complex(re=NaN,im=NaN) give what I expect > Re(complex(re=NaN, im=NaN)) [1] NaN > Im(complex(re=NaN, im=NaN)) [1] NaN > Arg(complex(re=NaN, im=NaN)) [1] NaN > Mod(complex(re=NaN, im=NaN)) [1] NaN > abs(complex(re=NaN, im=NaN)) [1] NaN and so do the following > Re(complex(re=1,

On Aug 15, 2010, at 5:12 PM, Silvio Ricardo Cordeiro wrote: > Is there a way for me to collect statistics about the number of loads/stores added by the "linearscan" register allocator (just like can be done with the "local" allocator)? I still haven't grokked very well the interaction between RALinScan and Spiller... Should I add those two statistics to the spiller's class? RALinearScan asks the Spiller to spill a virtual register. The StandardSpiller passes the request to LiveIntervals::addIntervalsForSpills. Here, the spill and restore points are...

It's probably toadally elementary (and, like, duhhhhh) but I can't figure out why the following doesn't work: curve(function(x){qnorm(x,4,25)},from=0,to=1) I get the error: Error in xy.coords(x, y, xlabel, ylabel, log) : 'x' and 'y' lengths differ But if I do foo <- function(x){qnorm(x,4,25)} curve(foo,from=0,to=1) it goes like a train. Also

...ng <zhangweiping at didichuxing.com> > > Cc: virtualization at lists.linux-foundation.org > > --- > > drivers/virtio/virtio_mmio.c | 43 +++++++++---------------------------------- > > 1 file changed, 9 insertions(+), 34 deletions(-) > > In the hope that I have grokked the devm_* interface by now, > > Reviewed-by: Cornelia Huck <cohuck at redhat.com> Thanks! Michael, could you please queue this as a fix for v4.15? This regressed arm64 VMs booting between v4.15-rc1 and v4-15-rc2, impacting our automated regression testing, and I'd very much lik...

...ng <zhangweiping at didichuxing.com> > > Cc: virtualization at lists.linux-foundation.org > > --- > > drivers/virtio/virtio_mmio.c | 43 +++++++++---------------------------------- > > 1 file changed, 9 insertions(+), 34 deletions(-) > > In the hope that I have grokked the devm_* interface by now, > > Reviewed-by: Cornelia Huck <cohuck at redhat.com> Thanks! Michael, could you please queue this as a fix for v4.15? This regressed arm64 VMs booting between v4.15-rc1 and v4-15-rc2, impacting our automated regression testing, and I'd very much lik...

Chris Lattner <clattner at apple.com> writes: > On Jul 28, 2011, at 2:16 PM, David A. Greene wrote: > Disagreed. The point is that I should not see a stream of 20 > decomposed patches from you. When I get to one that is "wrong" or > needs changes (e.g. patch 6), then all the other patches after it get > ignored. This is silly. It is silly. I see no reason to

On Jul 29, 2011, at 11:26 AM, David A. Greene wrote: >> Disagreed. The point is that I should not see a stream of 20 >> decomposed patches from you. When I get to one that is "wrong" or >> needs changes (e.g. patch 6), then all the other patches after it get >> ignored. This is silly. > > It is silly. I see no reason to simply ignore the later patches

I think y'all underestimate how important documentation can be. There are, after all, documents out there that purport to be guides to writing a back end for LLVM. I know of 2 other experienced & motivated compiler writers who read the available documentation, wrote some code, foundered, gave up, and wrote their own back end from scratch. So there's three of us that I know about, and I

I am just beginning to use LLVM, and find that 'getting started' is the steep part of the learning curve. I am using MingW and msys, which I have not fully grokked yet. Anyway, actually building the libraries from source is turning out to be difficult. I want to work with LLVM as described in the except from the LLVM FAQ below. I am using C++, so the FFI is a non-issue. Can someone supply me with a download link for a fully built LLVM OBJ_ROOT directory...

...ant to provide a way for the user to stop lli using the MCJIT; I think that's probably wise but maybe it's unnecessary. Anyway, this sounds like making a default choice based on a target-triple is something that probably ought to be done "using canonical idiom" so it's easily grokked rather than using an ad-hoc approach. Does anyone have any thoughts? Many thanks, David Tweed -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not dis...

On 25 September 2013 22:13, Preston Briggs <preston.briggs at gmail.com> wrote: > A lot of my difficulty in reading other examples is that it's not clear > what matters and what doesn't. It's what I hope to get by sitting next to > someone and asking questions. Some of this could be addressed in a guide. > I'd start with a chapter on planning. > Another

On Jul 28, 2011, at 2:16 PM, David A. Greene wrote: >>> The flow promoted by Git is precisely to make sure each and every commit >>> passes the tests. So, the granularity of "incremental development" is >>> really the commit, not how often you merge. >> This model is based on the idea of some trusted maintainer doing code >> review of the branch and