similar to: [LLVMdev] sizeof patch

I have this code: IEF <- to.monthly(IEF, indexAt="endof") SPY <- to.monthly(SPY, indexAt="endof") I would like to use a for loop instead of separate entries, so the only code that needs to be modified is the list of symbols. symbols <- c("IEF", "SPY") for(symbol in symbols) { symbol <- to.monthly(symbol, indexAt="endof") } This

Although linkspeed and duplex can be set in a linux guest via 'ethtool -s', this requires custom ethtool commands for virtio-net by default. Introduce a new feature flag, VIRTIO_NET_F_SPEED_DUPLEX, which allows the hypervisor to export a linkspeed and duplex setting. The user can subsequently overwrite it later if desired via: 'ethtool -s'. Linkspeed and duplex settings can be

Hi, I am trying to run an analysis of variance using R. in my data table "x" is a continuous variable lengthof 200 and "p" is a categorical variable also of length 200 and p is anyone of three categories 1,2 or ,3. if I run summary(aov(x~p,data=test)) I get Response: x Df Sum Sq Mean Sq F value Pr(>F) p 1 3174.7 3174.7 42.749 5.175e-10 ***

In prepartion for using some of the high order feature bits, make sure that virtio-net uses 64-bit values everywhere. Signed-off-by: Jason Baron <jbaron at akamai.com> Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> --- hw/net/virtio-net.c | 54 +++++++++++++++++++++--------------------- include/hw/virtio/virtio-net.h |

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I am working on a port of LLVM targeting a proprietary VM. Thus far > development has been under Linux and Cygwin. Cygwin licensing would appear > to require that LLVM built under Cygwin would have to be released under the > GPL, so alternatives are being investigated. I am not a lawyer, but: I think that you are misinterpreting the

On 2009-05-15, at 07:26, David Greene wrote: > On Friday 15 May 2009 05:50, Jay Foad wrote: >> > >>> The one major thing to be aware of is that it isn't safe to use >>> &V[0] when V is an empty std::vector >> >> Oh dear. That's a bit of a flaw in the plan. I suppose the solution >> is to switch to SmallVector whenever this might be a

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

Hi Christian, Chuck (and lists) It seems that the problem may be the strange behaviour of 'unstack' inside a function. See this thread in the R mailing list: http://tolstoy.newcastle.edu.au/R/help/04/03/1160.html Anyway, I got round the problem by using 'aggregate' instead of converting to a list and then tapply to sum values of metric. Probably more efficient as well. Thanks

Use macro definition Cc: Jeremy Fitzhardinge <jeremy at goop.org> Cc: Chris Wright <chrisw at sous-sol.org> Cc: virtualization at lists.linux-foundation.org Cc: linux-ia64 at vger.kernel.org Signed-off-by: Fabian Frederick <fabf at skynet.be> --- This is untested. arch/ia64/kernel/paravirt.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

Use macro definition Cc: Jeremy Fitzhardinge <jeremy at goop.org> Cc: Chris Wright <chrisw at sous-sol.org> Cc: virtualization at lists.linux-foundation.org Cc: linux-ia64 at vger.kernel.org Signed-off-by: Fabian Frederick <fabf at skynet.be> --- This is untested. arch/ia64/kernel/paravirt.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

gcc picked up a couple of suspicious memset lengths which turned out to be real bugs. Signed-off-by: Anton Blanchard <anton at samba.org> --- usr/kinit/nfsmount/sunrpc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/usr/kinit/nfsmount/sunrpc.c b/usr/kinit/nfsmount/sunrpc.c index 0628cef..0a7fcf5 100644 --- a/usr/kinit/nfsmount/sunrpc.c +++

Commit-ID: 71a849a7e2d5e73321e986fa91d1f34b387e71ba Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=71a849a7e2d5e73321e986fa91d1f34b387e71ba Author: Anton Blanchard <anton at samba.org> AuthorDate: Tue, 3 Dec 2013 18:14:58 +1100 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Tue, 3 Dec 2013 10:53:38 -0800 [klibc] nfsmount: memset uses sizeof

The code was passing sizeof(char *) - not the length of the buffer - to strlcpy and snprintf. Change the function to take the length of the buffer as a parameter. Fixes the warning: argument to 'sizeof' in 'snprintf' call is the same expression as the destination; did you mean to provide an explicit length? Signed-off-by: Jonathan Boeing <jonathan.n.boeing at gmail.com>

--- silk/dec_API.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/silk/dec_API.c b/silk/dec_API.c index b5acb6b..1c356c7 100644 --- a/silk/dec_API.c +++ b/silk/dec_API.c @@ -357,7 +357,7 @@ opus_int silk_get_TOC( return -1; } - silk_memset( Silk_TOC, 0, sizeof( Silk_TOC ) ); + silk_memset( Silk_TOC, 0, sizeof( silk_TOC_struct ) ); /* For

Looking through the IR documentation, I have been unable to establish if the size of a pointer value is knowable to an LLVM optimization pass. For an IR->IR optimization pass, is the pass allowed to assume anything about the size of a pointer value? Or is making such an assumption explicitly disallowed? Once target specific information gets introduced, I'm assuming that the size of

On 20 December 2013 22:44, Philip Reames <listmail at philipreames.com> wrote: > Looking through the IR documentation, I have been unable to establish if > the size of a pointer value is knowable to an LLVM optimization pass. > For an IR->IR optimization pass, is the pass allowed to assume anything > about the size of a pointer value? Or is making such an assumption >

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Rick Mann > Subject: [LLVMdev] Sizeof a type? > Is there a way to get the sizeof a type? Look at the methods of the DataLayout class. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you