similar to: [LLVMdev] Git/Svn numbers

Passing a memoryview we avoid unneeded copy of the original buffer. On the python side memoryview object can be used for slicing, writing to file, or sending to socket. This may break plugins assuming that the they get a bytearray, but good python code should not care about the type of the buffer, only about the behaviour. Testing with a plugin writing to /dev/null shows 2.7x speedup. Real

Greetings, I have 3 SLES 10 SP3 servers running Xen (3.2.3). The motherboard is a Tyan S3992 h2000M and I have dual quad-core AMD Opterons wit 8GiB RAM. The board''s BIOS is up to date. When I boot the Xen kernel, memory performance seems very slow: $ time memhog 100m mbind: Function not implemented get_mempolicy: Function not implemented .......... real 0m1.117s user 0m0.148s sys

I recently got a new SSD (ocz vertex LE 50gb) It seems to work really well as a ZIL performance wise. My question is, how safe is it? I know it doesn''t have a supercap so lets'' say dataloss occurs....is it just dataloss or is it pool loss? also, does the fact that i have a UPS matter? the numbers i''m seeing are really nice....these are some nfs tar times before

> So, to summarize: > Git clone is seven times faster than svn checkout for > the llvm and clang repositories. > Git repo size is half of svn repo size. Yeah, git is incredibly fast, even for huge project (like the linux kernel). For the way LLVM works, I can only see one drawback: it works always atomically with a whole tree. An example: if you have one git repository with

Alle, I'm following the instructions in section 19.3.3.2 of the docs @ http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-nfs-config-autofs-LDAP.html, but I cannot add the following entry in LDAP: dn: automountMapName=auto.home,dc=subaru,dc=nao,dc=ac,dc=jp objectClass: top objectClass: automountMap automountMapName: auto.home After looking at the schemas in /etc/openldap/schema,

The Wine maintenance release 3.0.1 is now available. What's new in this release (see below for details): - Various bug fixes - Translation updates The source is available from the following locations: https://dl.winehq.org/wine/source/3.0/wine-3.0.1.tar.xz http://mirrors.ibiblio.org/wine/source/3.0/wine-3.0.1.tar.xz Binary packages for various distributions will be available from:

The Wine development release 3.4 is now available. What's new in this release (see below for details): - More Vulkan support, including integration with the X11 driver. - Better handling of privileged instructions on x86-64. - Hex edit dialog improvements in RegEdit. - Assortment of patches merged from wine-staging. - Various bug fixes. The source is available from the following

Hi all, I''m new to shorewall and have been struggling with several problems for several days now. Most of them are solved, but one still persists. The firewall is running on my server under Debian Sarge (Kernel 2.6) I''ve got three network interfaces: ppp0 (DSL Internet) eth1 (lan) ath0 (wlan) eth1 and ath0 are bridged together to br0. The problem is, that Samba (also running

Hello! Is it possible to add window rotation like freewins to compiz, now that DRI2 is done? This way reading emails in bed would be very convenient. :) g

Hi! What about Debian/Ubuntu packages? This would significantly help using LLVM because a simple "aptitude install llvm" would install it ready for use. There are packages in Debian, but unfortunately they are very old (1.8). I tried to email the maintainer but got no response. Then I tried to update myself by "apt-get source llvm", "uupdate" and modifying Debian