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

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.

>>>>> Saikat DebRoy writes: > On Thursday, Sep 25, 2003, at 05:26 US/Eastern, CanisMaior@web.de wrote: >> Bugs compiling R-1.7.1 with Intel compilers icc and ifc, >> on x86-computer (Pentium IV) and linux operating system >> > Many of those bugs can be fixed by using appropriate configure options. > Some of the warnings are serious, but they quite a

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

Hello r-bugs, I am running openSuse 11.0, with my new Intel 8500 (Penryn) C2D, and I want to use icc and ifort. I was able to get a working Goto BLAS, following Dr. Goto's instructions. That seems to work OK with gcc and gfortran. I get about 10% faster computations by using -O3 rather than -O2. I get faster results with Goto BLAS rather than the R BLAS. Now I want to make icc and ifort

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

I am having trouble compiling R-2.6.2 on suse linux x86_64 using the intel compiler. I read section C.2.1 Intel compilers in the R Installation and Administration manual, and put CC=icc CFLAGS="-g -O3 -wd188 -ip" F77=ifort FFLAGS="-g -O3" ICC_LIBS=/opt/intel/cce/10.1.012/lib IFC_LIBS=/opt/intel/fce/10.1.012/lib/ LDFLAGS="-L$ICC_LIBS -L$IFC_LIBS -L/usr/lib64"

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,

Hi, I have built a library that consists of a piece of C code and some R functions. To build it into a library that I can load using library() command, I have followed "Writing R Extensions" and made sub-directories such as mylib/R and mylib/src. But when I run R CMD INSTALL mylib, nothing seems to be happening with src directory, i.e., no C compiling. I have probably missed some key

Hi, I have built a library that consists of a piece of C code and some R functions. To build it into a library that I can load using library() command, I have followed "Writing R Extensions" and made sub-directories such as mylib/R and mylib/src. But when I run R CMD INSTALL mylib, nothing seems to be happening with src directory, i.e., no C compiling. I have probably missed some key

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:

Win7, R2.11.0 I am working on a report together with several co-authors. The data concern several performance measures on a set of groups. These measures are scored by external judges. We report findings on several datasets, including several of the 6 ICC's discussed by Shrout & Fleiss (1979). We determine these using the icc function from the irr package. We have also used the ICC

Dear R users I would like to ask a question regarding to icc (intraclass correlation) or many biologists refer it to as repeatability. It is very useful to get icc for many reasons and it is easy to do so from linear mixed-effects models and many packages like psy, psychometric, aod and irr have functions to calculate icc. icc = between-group variance/(between-group variance + residual

Hello everyone. As some of you know, I was able to compile wine with Intel C++ Compiler (ICC), compilation log is located here: http://wine.x.pl/wine-1.1.38-ICC-compilation.log.tar.gz Some tests failed, and dxgi failed to compile (this is only related to DX10 I think), anyway all apps I tested worked fine (Red Faction 1 & 2, 3DMark 2000,2001SE,2003,Foobar2000,Operation Flashpoint), so I did

I am helping someone calculate ICC using R. I know R has several packages like irr, psy etc which provide options to calculate ICC (intraclass correlation coefficient). When getting ICC, we need to use the model: two-way mixed model with absolute agreement. I only found that in irr package, it provides the option of choosing one or two way and consistence or absolute agreement model. However,

Hi, all There are 62 samples in my data and I tested 3 times for each one, then I want to use ICC(intraclass correlation) from irr package to test the consistency among the tests. *combatexpdata_p[1:62] is the first text results and combatexpdata_p[63:124] * is the second one and *combatexpdata_p[125:186]* is the third. Here is the result:

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, >

I would appreciate some thoughts on using the bootstrap functions in the library "bootstrap" to estimate confidence intervals of ICC values calculated in lme. In lme, the ICC is calculated as tau/(tau+sigma-squared). So, for instance the ICC in the following example is 0.116: > tmod<-lme(CINISMO~1,random=~1|IDGRUP,data=TDAT) > VarCorr(tmod) IDGRUP = pdLogChol(1)

Dear developeRs, As of icc 10, the -c99 option is deprecated, and generates a lot of warnings when compiling R or R packages. If you use CC="icc -std=c99" instead of just CC="icc", R's configure will not add the -c99 option, and the code seems to compile and run just fine. (Please don't hesitate to let me know if this is a bad idea. :-) -- Regards, Bj?rn-Helge