search for: stringently

----- Original Message ----- > From: "Sebastian Pop via cfe-dev" <cfe-dev at lists.llvm.org> > To: "Renato Golin" <renato.golin at linaro.org> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Sebastian Paul Pop" <s.pop at samsung.com>, "Abe Skolnik" > <a.skolnik at samsung.com>, "cfe-dev"

Thanks a lot for pointing out the reason (and yes, I am testing quite to stringent in this case - it's my old testing disease ;-) For other readers: The R-devel NEWS is a good source to find possible change reasons: https://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html On Sun, 2019-09-29 at 08:33 -0400, Duncan Murdoch wrote: > On 29/09/2019 7:55 a.m., nospam at altfeld-im.de wrote:

Hi, i have used S4 classes to implement a unified access to random number generators (package rstream on CRAN). I have used a construct to allow optional arguments: if(!isGeneric("rstream.sample")) setGeneric("rstream.sample", function(stream,...) standardGeneric("rstream.sample")) setMethod("rstream.sample",

Hi all, Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source tarballs here: http://llvm.org/pre-releases/3.0/ A Word About Patches I neglected to send out instructions on how to get patches into the LLVM 3.0 branch. All patches must

Dear R-Help, I am using the function "topTable" from the LIMMA package. To estimate adjusted P-values there are several options (adjust="fdr" , adjust="BH") as shown below: topTable(fit, number = 10, adjust = "BH", fit$Name) I guess any of these options (fdr, BH, etc.) is using a default of FDR=0.05 which is quite conservative (i.e., very

Hi, I have a failing unit test in my package tryCatchLog on the CRAN build infrastructure (https://cran.r-project.org/web/checks/check_results_tryCatchLog.html) with "R Under development (unstable) (2019-09-27 r77229)" and the unit tests just ensures consistent behaviour of R (not of my package) as a precondition: The failing unit test is caused by >

Hello all, I have the following problem: I wish to access the NFS shares through Windows. I want guideline on the following issues : 1.One of the solution to above problem involves sharing the same share(directory) using Samba server and NFS server.But won't this give rise to conflicts with respect to access permission bits of that particular directory being shared. (Because Samba

Consider > summary(1:5) Min. 1st Qu. Median Mean 3rd Qu. Max. 1 2 3 3 4 5 > summary(c(1:5,NA)) Min. 1st Qu. Median Mean 3rd Qu. Max. NA's 1 2 3 3 4 5 1 Wouldn't it be more stringent if "NA's" was also reported in the first case?? Regards S?ren

Hi, Dovecot 2.3.1 (8e2f634). When using submission one client of mine can not send messages. Directly sending through exim works. Seems that dovecot is too picky or follow the RFC too precise here to be compatible. Here is the debug log (note the space between ?From:" and "<user2 at host.com>?): Apr 6 12:02:08 mail dovecot: submission(user at

Hi Bill, Do we have a list of which PRs have been filed that are considered release blockers? -Jim On Oct 17, 2011, at 4:33 PM, Bill Wendling wrote: > Hi all, > > Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source

A package I have written makes considerable use of external C code. There appear to be no problems building a Windows binary with the GNU C compiler, but now I would like to make the package available for other platforms. A stringent check of the code with the gcc options '-Wall -pedantic' flags many nested functions and variable-length arrays that are not allowed in ISO C. Is it

In current versions of R, pretty(333) gives an infinite loop (due to a silent integer overflow in src/appl/pretty.c). I've looked at this problem and also at what S-plus does, (no code there to inspect, just experiments), and then I have fixed pretty.c. I think that it now behaves much more reasonably (both than before and than S / S-plus). The only problem: pretty(.) is not

Hello, since Bioconductor devel branch 3.11 started, which is operating with R-devel 4.0.0 (for e.g. 2019-11-03 r77362 on OS X 10.11.6 El Capitan), my package CFAssay 1.21.0 is not built on none of all three Systems, Linux, Windos and Mac. The error message refers to xy.coords which is called by R function plot.default. I found out that it has to do with the S3 object system. In my package I

1/ Most correctly configured unix servers are fairly secure. Workstations on the other hand are extremely easy to compromise. Even if the eeprom (on a sparc) is password protected the fact that a hacker can get physical access to the machine means that it's very likely to be compromised, but thats just life. (I'm sure at least some readers on this list will at some time in there life have

Not yet. That is, I don't think any have been filed at all for 3.0. I don't know whether to be happy or worried. :-) Any that are regressions should be marked with the 'regression' keyword and be a release blocker. -bw On Oct 20, 2011, at 8:40 AM, Jim Grosbach wrote: > Hi Bill, > > Do we have a list of which PRs have been filed that are considered release blockers?

On Tue, 17 Apr 2012 08:38:18 -0400 Rafael Espíndola <rafael.espindola at gmail.com> wrote: > > It also has the problem that there's nothing preventing a > > pass like GVN from merging a !fpmath-decorated operation with an > > undecorated operation, and nothing requiring it to strip > > the !fpmath tag when it does so. (This is a general problem > > with

Maybe someone can help shed some light on an odd and repeatedly irritating error I noticed when running the check Perl script on my R 1.3 project. In following it line by line, I traced my problem down to the code/documentation matching within check, the most recent version of which seems to verify proper .Rd formatting by means of R's codoc and undoc functions. Under R --vanilla, those two

Having unsuccessfully browsed around the Wine FAQ for an answer, forgive my asking this directly ! Wouldn't it make a certain amount of sense to have separate Wine projects with partially shared codebases, to realise compatibility with the different flavours of Windows ? [I have not inspected the codebase, so excuse me if this is already the case.] In this way, you are not aiming at a

I'm interested in what we can do about TBAA for loads that the compiler inserts when optimizing loads into smaller loads (e.g. what SROA does). I'm gonna set the stage by using a small C snippet, because I think C has the best-understood implementation of TBAA among the folks on the list. However, I was unable to actually come up with an example where this inhibits optimizations coming

Hi Tim, On 01/ 8/14 10:24 PM, Tim Northover wrote: > Hi Karel, > >> I've observed the same issue with LLVM 3.4 as distributed by Ubuntu 13.10 >> and with LLVM HEAD compiled on January 6. I'm able to provide the byte-code >> file which results in this issue, but would first like to know if this is a >> known issue in AArch64 target support or if I shall submit