search for: nonoptimal

...al directories rm dest/a # At this point, a & b exist in src; only b exists in dest. rsync -aHv src/. dest/. building file list ... done ./ a b => a wrote 10241366 bytes read 36 bytes 6827601.33 bytes/sec total size is 20480000 speedup is 2.00 The above is BAD (nonoptimal) behavior; the entire file is transferred, even though it could simply have been linked. It seems that "a" is transferred before it is determined that a suitable equivalent (linked) file "b" already exists. I suspect that this has to do with handling the file list in a sort...

On Tue, May 18, 2010 at 7:04 PM, Roland Scheidegger <sroland at vmware.com> wrote: > Hi, > > I plan to merge the gallium-msaa branch to master soon. > It's actually a bit of a misnomer since the conceptually more important > changes in there are about blits... > > Here's a short summary what this is about: > blits now operate on resources, not surfaces

Hello, LLVMers. While making some bitcodes from HL source codes including loops, I came to wonder which was the better one for the optimization between: llvm-gcc -O4 .... (using llvm-gcc optimization) and llvm-gcc -O0 .... (nonoptimization of llvm-gcc) opt -mem2reg -instcombine -indvars .... (w/ optimization pass) After some trials, 'llvm-gcc -O4' seemed better for

food now? or after work in the library? On Wed, 2010-06-02 at 12:00 +0200, r-sig-debian-request at r-project.org wrote: > Send R-SIG-Debian mailing list submissions to > r-sig-debian at r-project.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://stat.ethz.ch/mailman/listinfo/r-sig-debian > or, via email, send a message with subject or body

Hi, Peter Lister <P.Lister at sychron.com> schrieb am 06.02.02: > In way way better and easier? When I have criticised pxelinux I think > I've always stated *why* etherboot seems better for our environment. > > I'm not trying to be religious, or get anyone to change a working system > - I'm genuinely interested what differences others perceive. I've looked

Hi All, Our team at Facebook is building a new context-sensitive Sample PGO as an alternative to the existing AutoFDO. We’d like to share our motivation, propose a new design, and reveal preliminary results on benchmarks. We will refer to the proposed design as CSSPGO in this RFC. The new CSSPGO leverages simultaneous LBR and stack sampling to construct a full context-sensitive profile. It