search for: 120400

ZVOL was recently converted to use range locking, but it seems the comment below wasn''t updated: /* * There must be no buffer changes when doing a dmu_sync() * because * we can''t change the data whilst calculating the checksum. * A better approach than a per zvol rwlock would be to lock * ranges. */ -- Pawel Jakub Dawidek http://www.wheel.pl

I'd look at if_spppsubr.o, which is big in the llvm directories and doesn't appear in the gcc directory listings at all (I assume the listings were fed through tail or something, but there's clearly a sizeable difference there) On Jul 17, 2009, at 5:41 PMPDT, Daniel Dunbar wrote: > On Fri, Jul 17, 2009 at 5:12 PM, Jonathan Gray<jsg at goblin.cx> wrote: >> On

...n/a MultiSource/Benchmarks/Prolangs-C/unix-smail/unix-smail | 0.2418 59936 0.3557 * 0.2565 | 0.01 0.00 0.00 * 0.28 | - - n/a n/a MultiSource/Benchmarks/Prolangs-C/unix-tbl/unix-tbl | 0.4623 120400 0.6104 * 0.2253 | 0.00 0.00 0.00 * 0.26 | - - n/a n/a MultiSource/Benchmarks/Ptrdist/anagram/anagram | 0.0552 10656 0.0481 * 0.0466 | 2.25 2.51 2.38 * 2.39 |...

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download