search for: out

Tu fichero tiene los decimales como puntos y no como comas como tu le indicas. Te dejo un ejemplo #--------------------------------------------------------------------------------------------------------------------- setwd(dir="c:/Users/usuario/Desktop/") library(outliers) filename<-"timediff.csv" time<-read.csv(filename, sep=";",header=TRUE,dec=".") # Esto es lo que has de cambiar chisq.out.test(time$TimeDiff) # Ayuda adicional #--------------------------------------------------------------------- # Si no supones normalida...

...lidación) que de un test. De todas maneras seguro que tienes un informe de como recogiste los datos y puedes trazar el origen de este dato en concreto. Creo que eso es mejor que cualquier test. De todas maneras a mi el test me sale: > setwd(dir="c:/Users/usuario/Desktop/")> library(outliers)> filename<-"timediff.csv"> time<-read.csv(filename, sep=";",header=TRUE,dec=".") # Esto es lo que has de cambiar> chisq.out.test(time$TimeDiff) chi-squared test for outlier data: time$TimeDiff X-squared = 73260.07, p-value < 2.2e-16 alternati...

...gt; MachineBasicBlock::iterator EndItr) { >> - assert(MBB->end() == EndItr&& "Bad EndIndex"); >> - >> - SchedulerImpl->enterRegion(MBB, BeginItr, EndItr, MBB->size()); >> - >> - // Build the DAG without reordering instructions. >> - SchedulerImpl->schedule(); >> - >> - // Remember scheduling units. >> - SUnits = SchedulerImpl->SUnits; >> + assert(VLIWScheduler&& "VLIW Scheduler is not initialized!"); >> + VLIWScheduler->enterRegi...

There is some redundancy at the instruction format level in the x86 .td files. For example, in X86InstrFormats.td: // SSE1 Instruction Templates: // // SSI - SSE1 instructions with XS prefix. class SSI<bits<8> o, Format F, dag outs, dag ins, string asm, list<dag> pattern> : I<o, F, outs, ins, asm, pattern>, XS, Requires<[HasSSE1]>; // SSE3 Instruction Templates: // S3SI - SSE3 instructions with XSrefix. class S3SI<bits<8> o, Format F, dag outs, dag ins, string asm, list<dag>...

Hi, This patch fixes outs/ins of MOV16mr instruction of X86. Thanks. diff --git a/lib/Target/X86/X86InstrInfo.td b/lib/Target/X86/X86InstrInfo.td index e9a0431..f5b2064 100644 --- a/lib/Target/X86/X86InstrInfo.td +++ b/lib/Target/X86/X86InstrInfo.td @@ -1412,7 +1412,7 @@ let SchedRW = [WriteStore] in { def MOV8mr : I&...

...David Greene wrote: > There is some redundancy at the instruction format level in the x86 .td > files. For example, in X86InstrFormats.td: > > // SSE1 Instruction Templates: > // > // SSI - SSE1 instructions with XS prefix. > > class SSI<bits<8> o, Format F, dag outs, dag ins, string asm, list<dag> > pattern> > > : I<o, F, outs, ins, asm, pattern>, XS, Requires<[HasSSE1]>; > > // SSE3 Instruction Templates: > // S3SI - SSE3 instructions with XSrefix. > > class S3SI<bits<8> o, Format F, dag outs, d...

We've had this argument before. IMO LLVM should not be in the business of closing stdout, and no code in lib/ should print to stdout because users may expect output there (-o -). On Fri, Jan 23, 2015 at 10:20 AM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2015-Jan-23, at 09:52, mats petersson <mats at planetcatfish.com> wrote: > > &g...

On Jun 1, 2012, at 7:41 PM, Justin Holewinski wrote: > > > > Unfortunately, the use of outs() and (especially) errs() is rampant - a simple grep of the 3.1 source tree shows about 1,500 instances. One of the first things we had to implement in order to make LLVM usable is something very similar to what Justin has proposed. Centralizing control of the output in outs()/errs() would seem...

I was just fixing a bug that was caused by `stdout` being closed before the runtime has done `fflush(stdout)` [or however this is implemented in the runtime]. The cause of this seems to be that `outs()` returns a static object created from `raw_fd_stream(STDOUT_FILENO, true)` - the `true` being the `shouldClose` parameter. Surely LLVM is not supp...

On Fri, Jun 1, 2012 at 10:17 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jun 1, 2012, at 7:41 PM, Justin Holewinski wrote: > > > >> > Unfortunately, the use of outs() and (especially) errs() is rampant - a >> simple grep of the 3.1 source tree shows about 1,500 instances. One of the >> first things we had to implement in order to make LLVM usable is something >> very similar to what Justin has proposed. Centralizing control of the >>...

Dear all, Consider there is a program that writes to stdout using two different raw_fd_ostream-s: #include "llvm/LLVMContext.h" #include "llvm/Module.h" #include "llvm/Support/raw_ostream.h" using namespace llvm; int main() { raw_fd_ostream S(STDOUT_FILENO, false); outs() << "Hello";...

Hi all, Tentatively final version is up here: https://reviews.llvm.org/D25587 It has a verbal LGTM, but I plan to wait a bit longer just in case anyone has some additional thoughts. It's a large patch, but if you're interested, one way you can help without doing a full-blown review is to look at the large comment blocks in FormatVariadic.h and FormatProviders.h. Here I provide a formal description of the grammar of the replacement sequences and format syntax. So you can look at this without looking at the code behind it and see if you have comments...

Hi Dan, Sean, Thanks for replies, So does it mean user is not expected to use any other stream for stdout, but outs()? Although there is a comment "If you don't want this behavior, don't use outs().", outs() is a static instance which always exists and creates problems, even if not used. - D. 2012/11/29 Dan Gohman <dan433584 at gmail.com> > On Wed, Nov 28, 2012 at 10:54 PM...

hello, are there functions to detecte outlying observations in samples? thanks. ___________________________________________________________________________ [[alternative HTML version deleted]]

On 12.10.2016 05:59, Mehdi Amini via llvm-dev wrote: >> If you change a const char * to a StringRef, it can silently succeed >> while passing your StringRef object to printf. It should fail to compile! > > llvm::format now fails to compile as well :) > > However this does not address other issues, like: `format(“%d”, float_var)` This may be a good time to point at

On Jun 1, 2012, at 7:08 PM, Caldarale, Charles R wrote: >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner >> Subject: Re: [LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs() > >> It would be much better for the linker to return its error in a proper way >> (i.e. extending llvm/Support/system_error.h like llvm/Object/Error.h does). > >> The right fix for this is to fix the code to not report errors textually. > > Unfortunately,...

On Wed, Nov 28, 2012 at 10:54 PM, Dmitry N. Mikushin <maemarcus at gmail.com>wrote: > Dear all, > > Consider there is a program that writes to stdout using two different > raw_fd_ostream-s: raw_fd_ostream does buffered I/O, so it's not really meant to be used like this. > #include "llvm/LLVMContext.h" > #include "llvm/Module.h" > #include "llvm/Support/raw_ostream.h" > > using namespace llv...

...wrote: > > On Jun 1, 2012, at 7:08 PM, Caldarale, Charles R wrote: > > >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Chris Lattner > >> Subject: Re: [LLVMdev] [llvm-commits] [PATCH] Allow per-thread > re-direction of outs()/errs() > > > >> It would be much better for the linker to return its error in a proper > way > >> (i.e. extending llvm/Support/system_error.h like llvm/Object/Error.h > does). > > > >> The right fix for this is to fix the code to not report errors &gt...

I am trying to make some modifications to our code generator that will produce better code, but require adding new patterns. What I am trying to do is take a register/register pattern and change it to a register/immediate. So for example, I have this pattern: class ILFormat<ILOpCode op, dag outs, dag ins, string asmstr, list<dag> pattern> : Instruction { let Namespace = "AMDIL"; dag OutOperandList = outs; dag InOperandList = ins; ILOpCode operation = op; let Pattern = pattern; let AsmString = !strconcat(asmstr, "\n"); bit has...

On Jun 1, 2012, at 11:13 PM, Justin Holewinski wrote: >> In a way, they are. What if I want a debug trace in a multi-threaded context? Right now, all threads would just spew to the same stream and the result would be unreadable. If you allow threads to setup their own outs() and errs() streams (transparently to the rest of LLVM), you can intercept these as you see fit, perhaps dumping each to a separate file. I acknowledge that you could also enforce single-threaded execution for debug runs, but what if you are in the context of a library with no valid stdout/stder...