similar to: Bugs compiling R-1.7.1 with Intel compilers icc and ifc (PR#4314)

Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.

>>>>> CanisMaior writes: > Bugs compiling R-1.7.1 with Intel compilers icc and ifc, > on x86-computer (Pentium IV) and linux operating system > Hello, > as there aren't many reports about that issue, I'll give a little > report here. (Hope I don't bother anyone) > The best thing about using icc and ifc are the warnings, because > it is said that

Dear R-devel, I'm trying to compile R-1.9.0beta (2004-03-31) with the PGI compilers (15-day free evaluation: after the 15 days the binaries will stop working). I'm running into some problems, that I hope some can offer pointers. 1. After configure, the FLIBS include /usr/local/lib' --- note the extra '. I had to manually delete it in a couple of places. In a previous thread on

> From: Prof Brian Ripley [mailto:ripley@stats.ox.ac.uk] > > On Fri, 2 Apr 2004, Liaw, Andy wrote: > > > Dear R-devel, > > > > I'm trying to compile R-1.9.0beta (2004-03-31) with the PGI > compilers > > (15-day free evaluation: after the 15 days the binaries > will stop working). > > I'm running into some problems, that I hope some can

On 2019/10/16 ??9:36, Zhu Lingshan wrote: > failed to send to kvm list, resend, sorry for the inconvenience. > > THanks, > BR > Zhu Lingshan > > On 10/16/2019 9:30 AM, Zhu Lingshan wrote: >> Hi all: >> ? This series intends to introduce Intel IFC VF NIC driver for Vhost >> Data Plane Acceleration. >> ? Here comes two main parts, one is ifcvf_base layer,

On 2019/10/22 ??2:53, Zhu Lingshan wrote: > > On 10/21/2019 6:19 PM, Jason Wang wrote: >> >> On 2019/10/21 ??5:53, Zhu, Lingshan wrote: >>> >>> On 10/16/2019 6:19 PM, Jason Wang wrote: >>>> >>>> On 2019/10/16 ??9:30, Zhu Lingshan wrote: >>>>> This commit introduced IFC VF operations for vdpa, which complys to

On 2019/10/23 ??2:19, Zhu, Lingshan wrote: > > On 10/22/2019 9:05 PM, Jason Wang wrote: >> >> On 2019/10/22 ??2:53, Zhu Lingshan wrote: >>> >>> On 10/21/2019 6:19 PM, Jason Wang wrote: >>>> >>>> On 2019/10/21 ??5:53, Zhu, Lingshan wrote: >>>>> >>>>> On 10/16/2019 6:19 PM, Jason Wang wrote:

On Thu, Mar 26, 2020 at 3:08 PM Jason Wang <jasowang at redhat.com> wrote: > > From: Zhu Lingshan <lingshan.zhu at intel.com> > > This commit introduced two layers to drive IFC VF: > > (1) ifcvf_base layer, which handles IFC VF NIC hardware operations and > configurations. > > (2) ifcvf_main layer, which complies to VDPA bus framework, >

On 2019/10/22 ??12:31, Simon Horman wrote: > On Mon, Oct 21, 2019 at 05:55:33PM +0800, Zhu, Lingshan wrote: >> On 10/16/2019 5:53 PM, Simon Horman wrote: >>> Hi Zhu, >>> >>> thanks for your patch. >>> >>> On Wed, Oct 16, 2019 at 09:10:40AM +0800, Zhu Lingshan wrote: > ... > >>>> +static void ifcvf_read_dev_config(struct

Dear List, While trying to define a customised CITATION file for a package, following R-exts, I realised that if I use only one 'citEntry' I got both a text description and a BibTex entry for the package, as for the 'nlme' package: -------------------------- citation('nlme') To cite package 'nlme' in publications use: Jose Pinheiro, Douglas Bates, Saikat

On 2019/10/21 ??5:53, Zhu, Lingshan wrote: > > On 10/16/2019 6:19 PM, Jason Wang wrote: >> >> On 2019/10/16 ??9:30, Zhu Lingshan wrote: >>> This commit introduced IFC VF operations for vdpa, which complys to >>> vhost_mdev interfaces, handles IFC VF initialization, >>> configuration and removal. >>> >>> Signed-off-by: Zhu Lingshan

On 2019/10/16 ??9:30, Zhu Lingshan wrote: > This commit introduced IFC VF operations for vdpa, which complys to > vhost_mdev interfaces, handles IFC VF initialization, > configuration and removal. > > Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> > --- > drivers/vhost/ifcvf/ifcvf_main.c | 541 +++++++++++++++++++++++++++++++++++++++ > 1 file changed, 541

Hello- I understand that it's convention, when comparing two models using the anova function anova(model1, model2), to put the more "complicated" (for want of a better word) model as the second model. However, I'm using lme in the nlme package and I've found that the order of the models actually gives opposite results. I'm not sure if this is supposed to be the case

On 2019/10/16 ??9:30, Zhu Lingshan wrote: > This commit introduced ifcvf_base layer, which handles IFC VF NIC > hardware operations and configurations. It's better to describe the difference between ifc vf and virtio in the commit log or is there a open doc for this? > > Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> > --- >

Forgive me if this isn't relevant, but: are you stripping off the output you need (e.g., parameter estimates) and throwing away what you don't (e.g., residuals)? Reid Huntsinger -----Original Message----- From: Saikat DebRoy [mailto:saikat at stat.wisc.edu] Sent: Wednesday, March 21, 2001 12:15 PM To: Han Lai Cc: R-help Subject: Re: [R] Is there any help for "Cannot allocate vector

----- Original Message ----- > This commit introduced IFC operations for vdpa, which complys to > virtio_mdev and vhost_mdev interfaces, handles IFC VF > initialization, configuration and removal. > > Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> > --- > drivers/vhost/ifcvf/ifcvf_main.c | 605 > +++++++++++++++++++++++++++++++++++++++ > 1 file changed,

Full_Name: Danny van Dyk Version: R-2.2.0 OS: Gentoo/AMD64 Submission from: (NULL) (83.129.50.65) I have successfully compiled R-2.2.0 using ifc-9.0.026 on my x86_64 box. The only (minor) change that hade to be made was adding fpicflags="-fPIC" to configure.ac in case F77 matches either "ifc" (old name) or "ifort" (new name). Please apply following patch: dvandyk

On 2019/10/21 ??6:00, Zhu, Lingshan wrote: > > On 10/16/2019 4:40 PM, Jason Wang wrote: >> >> On 2019/10/16 ??9:30, Zhu Lingshan wrote: >>> This commit introduced ifcvf_base layer, which handles IFC VF NIC >>> hardware operations and configurations. >> >> >> It's better to describe the difference between ifc vf and virtio in >> the

The Rows function which is called from plot.compareFits in the nlme package is not found. > plot(compareFits(coef(bp.model3),coef(bp.model3M))) Error in plot.compareFits(compareFits(coef(bp.model3), coef(bp.model3M))) : couldn't find function "Rows" > Can I find it elswhere? Have I missed a required package? Thanks Ross Darnell > library(help=nlme) nlme

Hello R-help I am having trouble getting gls to find the R objects that comprise a linear model when the data=named.object option(option!) is not specified. In the gls() help it states data is "an optional data frame containing the variables named in model, correlation, weights, and subset. By default the variables are taken from the environment from which gls is called". An example: