search for: logf

Hi List, I am trying to write unsuccessfully to a logfile with cat. Here my example code: letters[1:5]->x logf<-"test.txt" cat('%%%%%%%%%%%%%%%%%%%%%%%%%%\n',file=logf) catf<-function(x,...,logfile='log.txt', append=TRUE){ cat(x,'\n', file=logfile, append=append)} testit<-function(x,...){ paste0('thi...

Hi, I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized: http://llvm.org/releases/3.9.0/docs/Vectorizers.html#vectorization-of-function-calls When running with "clang -O3 -march=x86-64 -mavx2 -ffast-math test.c -S -emit-llvm", the function calling fabsf is vect...

...t; Hi, > I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. > > I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized: http://llvm.org/releases/3.9.0/docs/Vectorizers.html#vectorization-of-function-calls <http://llvm.org/releases/3.9.0/docs/Vectorizers.html#vectorization-of-function-calls> > > When running with "cl...

...gt; I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. >> >> I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized: http://llvm.org/releases/3.9.0/docs/Vectorizers.html#vectorization-of-function-calls <http://llvm.org/releases/3.9.0/docs/Vectorizers.html#vectorization-of-function-calls> >> >> When running with...

Oh nice, I can reproduce it here too, although only if I first load the 'logfs' module. It does seem to be a plain bug in the logfs module. Do you mind if I post the 1MB image you sent me into a public kernel bug report? Rich. ---------------------------------------------------------------------- mount -o -t logfs /dev/vda /sysroot/ [ 107.679255] BUG: unable to ha...

Hi all. I found next code when switch instruction differs: Engine.logf("right switch has extra case %r") << CaseValue; Where CaseValue is a ConstantInt object. Looking how logf works I found that it invokes DiffConsumer::printValue method for CaseValue. And here I found that CaseValue itself will never printed. On first look how DiffConsumer::print...

Hi, Please find the attached patch for review. -Stepan. John McCall wrote: > On Oct 28, 2011, at 2:00 AM, Stepan Dyatkovskiy wrote: >> I found next code when switch instruction differs: >> >> Engine.logf("right switch has extra case %r")<< CaseValue; >> >> Where CaseValue is a ConstantInt object. Looking how logf works I found >> that it invokes DiffConsumer::printValue method for CaseValue. And here >> I found that CaseValue itself will never printed. On fi...

On Oct 28, 2011, at 2:00 AM, Stepan Dyatkovskiy wrote: > I found next code when switch instruction differs: > > Engine.logf("right switch has extra case %r") << CaseValue; > > Where CaseValue is a ConstantInt object. Looking how logf works I found > that it invokes DiffConsumer::printValue method for CaseValue. And here > I found that CaseValue itself will never printed. On first look how...

Dear List: Is any one aware of a package that would extend the D() function and allow for one to maximize a likelihood function symbolically? Something akin to Solve[x==0, parameter] function in Mathematica? Clearly R has the capacity to _compute_ MLEs given a set of data. But, I'm looking for a package that would allow for me to define the likelihood function, find the 1st order partial

Dear all, I would like to log the calls to my functions. I am trying to do this using the function match.call(): fTest<-function(x) { theCall<-match.call() print(theCall) return(x) } > fTest(2) fTest(x = 2) [1] 2 I can see "theCall" printed into the console, but I don't manage to convert it into a character to write it into a log file

this patch adds a LogFile option to sshd_config. it just logs messages directly to a file instead of stderr or syslog. the largest change is an additional argument to log_init() in log.c for the log file name (and then changes to the rest of the tools to add a NULL arg). galt -------------- next part -------------- diff...

.... Stepan Dyatkovskiy wrote: > Hi, > > Please find the attached patch for review. > > -Stepan. > > John McCall wrote: >> On Oct 28, 2011, at 2:00 AM, Stepan Dyatkovskiy wrote: >>> I found next code when switch instruction differs: >>> >>> Engine.logf("right switch has extra case %r")<< CaseValue; >>> >>> Where CaseValue is a ConstantInt object. Looking how logf works I found >>> that it invokes DiffConsumer::printValue method for CaseValue. And here >>> I found that CaseValue itself will never...

...to target older glibc by having a C file containing: __asm__(".symver powf,powf at GLIBC_2.2.5"); __asm__(".symver expf,expf at GLIBC_2.2.5"); __asm__(".symver exp2f,exp2f at GLIBC_2.2.5"); __asm__(".symver log2f,log2f at GLIBC_2.2.5"); __asm__(".symver logf,logf at GLIBC_2.2.5"); __asm__(".symver log,log at GLIBC_2.2.5"); __asm__(".symver log2,log2 at GLIBC_2.2.5"); __asm__(".symver exp,exp at GLIBC_2.2.5"); __asm__(".symver exp2,exp2 at GLIBC_2.2.5"); __asm__(".symver pow,pow at GLIBC_2.2.5");...

...ties p0_s0 <- (1 - p_s1_s1) / (2 -p_s0_s0 -p_s1_s1) p0_s1 <- 1-p0_s0 # create variables p_s0_t_1 <- rep(0, nrow(X)) p_s1_t_1 <- rep(0, nrow(X)) p_s0_t <- rep(0, nrow(X)) p_s1_t <- rep(0, nrow(X)) f_s0 <- rep(0,nrow(X)-1) f_s1 <- rep(0,nrow(X)-1) f <- rep(0,nrow(X)-1) logf <- rep(0, nrow(X)-1) p_s0_t[1] <- p0_s0 p_s1_t[1] <- p0_s1 # initiate hamilton filter for(i in 2:nrow(X)) { # calculate prior probabilities using the TPT # TPT for this example gives us # p_si_t_1 = p_si_t_1_si * p_si_t + p_si_t_1_sj * p_si_t # where p_si_t_1 is the prob state_t = i...

...ork with > old glibc. I have one .cpp file with: __asm__(".symver powf,powf at GLIBC_2.2.5"); __asm__(".symver expf,expf at GLIBC_2.2.5"); __asm__(".symver exp2f,exp2f at GLIBC_2.2.5"); __asm__(".symver log2f,log2f at GLIBC_2.2.5"); __asm__(".symver logf,logf at GLIBC_2.2.5"); __asm__(".symver log,log at GLIBC_2.2.5"); __asm__(".symver log2,log2 at GLIBC_2.2.5"); __asm__(".symver exp,exp at GLIBC_2.2.5"); __asm__(".symver exp2,exp2 at GLIBC_2.2.5"); __asm__(".symver pow,pow at GLIBC_2.2.5");...

...gt; > > >__asm__(".symver powf,powf at GLIBC_2.2.5"); > >__asm__(".symver expf,expf at GLIBC_2.2.5"); > >__asm__(".symver exp2f,exp2f at GLIBC_2.2.5"); > >__asm__(".symver log2f,log2f at GLIBC_2.2.5"); > >__asm__(".symver logf,logf at GLIBC_2.2.5"); > > > >__asm__(".symver log,log at GLIBC_2.2.5"); > >__asm__(".symver log2,log2 at GLIBC_2.2.5"); > >__asm__(".symver exp,exp at GLIBC_2.2.5"); > >__asm__(".symver exp2,exp2 at GLIBC_2.2.5"); > >...

> On 23 Nov 2015, at 22:30 , aixtools <aixtools at gmail.com> wrote: > >> >> ./configure --enable-maintainer-mode ... Two things here - possibly irrelevant, but I'd avoid building in the source directory. (mkdir ../BUILD ; cd ../BUILD; ../R/configure) - don't turn on mantainer mode. You are not a maintainer, and if you want to play at being one, I think you

...gt; > > __asm__(".symver powf,powf at GLIBC_2.2.5"); > > __asm__(".symver expf,expf at GLIBC_2.2.5"); > > __asm__(".symver exp2f,exp2f at GLIBC_2.2.5"); > > __asm__(".symver log2f,log2f at GLIBC_2.2.5"); > > __asm__(".symver logf,logf at GLIBC_2.2.5"); > > > > __asm__(".symver log,log at GLIBC_2.2.5"); > > __asm__(".symver log2,log2 at GLIBC_2.2.5"); > > __asm__(".symver exp,exp at GLIBC_2.2.5"); > > __asm__(".symver exp2,exp2 at GLIBC_2.2.5"); >...

...ave one .cpp file with: > > __asm__(".symver powf,powf at GLIBC_2.2.5"); > __asm__(".symver expf,expf at GLIBC_2.2.5"); > __asm__(".symver exp2f,exp2f at GLIBC_2.2.5"); > __asm__(".symver log2f,log2f at GLIBC_2.2.5"); > __asm__(".symver logf,logf at GLIBC_2.2.5"); > > __asm__(".symver log,log at GLIBC_2.2.5"); > __asm__(".symver log2,log2 at GLIBC_2.2.5"); > __asm__(".symver exp,exp at GLIBC_2.2.5"); > __asm__(".symver exp2,exp2 at GLIBC_2.2.5"); > __asm__(".symver pow...

...asm__(".symver powf,powf at GLIBC_2.2.5"); > > >__asm__(".symver expf,expf at GLIBC_2.2.5"); > > >__asm__(".symver exp2f,exp2f at GLIBC_2.2.5"); > > >__asm__(".symver log2f,log2f at GLIBC_2.2.5"); > > >__asm__(".symver logf,logf at GLIBC_2.2.5"); > > > > > >__asm__(".symver log,log at GLIBC_2.2.5"); > > >__asm__(".symver log2,log2 at GLIBC_2.2.5"); > > >__asm__(".symver exp,exp at GLIBC_2.2.5"); > > >__asm__(".symver exp2,exp2 at GLIB...