search for: outs

...uot;,header=TRUE,dec=".") # Esto es lo que has de cambiar chisq.out.test(time$TimeDiff) # Ayuda adicional #--------------------------------------------------------------------- # Si no supones normalidad #--------------------------------------------------------------------- time.without.outs <- data.frame(row.names= 1:dim(time)[1], dif = time ) x <- boxplot(time.without.outs$TimeDiff,range= 1.5) # Quita los outliers que se van más de 1.5 rangos itercuartilicios. Puedes poner otro criterio pero este es el habitual time.without.outs$out.rg <- F time.without.outs[ time.without...

...t;> chisq.out.test(time$TimeDiff) >> >> >> # Ayuda adicional >> #--------------------------------------------------------------------- >> # Si no supones normalidad >> #--------------------------------------------------------------------- >> time.without.outs <- data.frame(row.names= 1:dim(time)[1], dif = time ) >> >> >> x <- boxplot(time.without.outs$TimeDiff,range= 1.5) # Quita los outliers >> que se van más de 1.5 rangos itercuartilicios. Puedes poner otro criterio >> pero este es el habitual >> >> time...

...@@ void HexagonAsmPrinter::printPredicateOperand(const MachineInstr *MI, >> /// the current output stream. >> /// >> void HexagonAsmPrinter::EmitInstruction(const MachineInstr *MI) { >> - MCInst MCI; >> - >> - HexagonLowerToMC(MI, MCI, *this); >> - OutStreamer.EmitInstruction(MCI); >> + if (MI->isBundle()) { >> + std::vector<const MachineInstr*> BundleMIs; >> + >> + const MachineBasicBlock *MBB = MI->getParent(); >> + MachineBasicBlock::const_instr_iterator MII = MI; >> + ++MII; >&gt...

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

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&l...

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

...son <mats at planetcatfish.com> wrote: > > > > 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 supposed to close `stdout` as part of its operations? > > Looks like this was added in r111643: > > com...

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

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 supposed to close `stdout` as part of its operations? -- Mats

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

...er 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"; S << ", world!"; return 0; } With this layout everything is fine, it prints ", world!Hello" Now, make S definition global: #include "llvm/LLVMContext.h" #include "llvm/Module.h" #include "llvm/Suppo...

...lacement sequences and format syntax. So you can look at this without looking at the code behind it and see if you have comments just on the format language. Here's a summary of (most) everything contained in this patch: 1) UDL Syntax for outputting to a stream or converting to a string. outs() << "{0}"_fmt.stream(1) std::string S = "{0}"_fmt.string(1); 2) Built-in format providers for various common types: outs() << "{0}"_fmt.stream("test"); // "test" outs() << "{0}"_fmt.stream(Stri...

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, Dmitry N...

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

...meant to be used like this. > #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"; > S << ", world!"; > > return 0; > } > > With this layout everything is fine, it prints ", world!Hello" > Yes. raw_ostream does buffering. The output you see is a classic symptom of having two different bu...

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

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

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/stderr...