similar to: [LLVMdev] any chance this icc circular dependency bug will get fixed for 2.7?

On Fri, Mar 5, 2010 at 5:53 AM, George Giorgidze <giorgidze at gmail.com> wrote: > > Hi Erick, > > Can you make the following functions available in llvm-c. > > createStandardFunctionPasses > createStandardModulePasses > createStandardLTOPasses > > Thanks in advance, George This is a little tricky, so I need some advice from the community. First off, I'm

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'm not a LLVM developer, but I'll give it a try... On Wed, Jun 4, 2008 at 9:12 AM, Talin <viridia at gmail.com> wrote: > I went and added a new file to the "Support" > directory (in include and lib). However, when I try to compile it, it > complains of a circular dependency error between libCore and libSupport: > > find-cycles.pl: Circular dependency

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,

In that scenario, I would expect that QCA would suggest Venn and Venn would suggest QCA. Then there's no circular dependency problem. Hadley On Fri, Apr 8, 2016 at 6:59 AM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Mark, > > Uhm... sometimes this is not always possible. > For example I have a package QCA which produces truth tables (all > combinations of

I've pretty much finished exposing all I wanted to llvm-c and the ocaml bindings for the soon to be released 2.7. Does anyone need any other functions exposed before the code freeze on the 7th?

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:

Dear Dmitri, If it's only a small number of functions then move them the relevant functions for A to B so that B works without A. Then Import these functions from B in A. Hence A depends on B but B is independent of A. It is requires to move a lot of functions than you better create a package C with all the common functions. Then A and B import those functions from C. Best regards, ir.

At the risk of stating the over-obvious: there's also the option of creating just a single package containing all functions. None of the functions that create the interdependencies need to be exported that way. Btw, his question is probably better at home at the r-package-devel list. Best, M On Thu, Apr 7, 2016, 22:24 Dmitri Popavenko <dmitri.popavenko at gmail.com> wrote: >

> but this strategy quickly inflates the number of packages on CRAN. CRAN contains 8210 packages today, so I would not worry about adding an extra one. Also, I think several small packages are preferable to one large one because attaching a big one just to get the one or two functions you want is also a waste. Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Apr 7, 2016 at 1:22 PM,

CodeGen, since it depends on MachineModuleInfo. On 2008-06-05, at 04:06, Talin wrote: > HyperQuantum wrote: >> I'm not a LLVM developer, but I'll give it a try... >> >> On Wed, Jun 4, 2008 at 9:12 AM, Talin <viridia at gmail.com> wrote: >> >> >>> I went and added a new file to the "Support" >>> directory (in include and

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

Well, I'm not saying that Dmitri _should_ do it. I merely mention it as an option that I think is worth thinking about -- it is easy to overlook the obvious :-). Since we have no further info on the package's structure we can't be sure.. Op vr 8 apr. 2016 om 13:59 schreef Adrian Du?a <dusa.adrian at unibuc.ro>: > Hi Mark, > > Uhm... sometimes this is not always

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

So I decided to bundle up the small amount of work I've done on generating source-level debugging info into a DebugInfoBuilder class like I described earlier. I went and added a new file to the "Support" directory (in include and lib). However, when I try to compile it, it complains of a circular dependency error between libCore and libSupport: find-cycles.pl: Circular

Another, perhaps slightly off the wall reframing of the 3-package possibility: Have packages B, a, and UserFacingA, as follows *a* contains all the functionality in your A package that *does not depend on B* *B* *imports from* *a* and is essentially unchanged *UserFacingA* *Depends* on *a* and *imports from* *B*, it implements all functionality from your package A that *does depend on* *B*, and

Erick Tryzelaar <erick.tryzelaar <at> gmail.com> writes: > > I've pretty much finished exposing all I wanted to llvm-c and the > ocaml bindings for the soon to be released 2.7. Does anyone need any > other functions exposed before the code freeze on the 7th? > Hi Erick, Can you make the following functions available in llvm-c. createStandardFunctionPasses