search for: _highly_

Having spent more time than I care to imagine waiting for 'opt' to link, I finally got frustrated enough to do something about it. As it turns out, the problem was already fixed. If you're working on LLVM, and using the GNU linker, I _highly_ _highly_ _highly_ recommend grabbing the CVS version of binutils (http://sources.redhat.com/binutils/) and using it. For me, it reduced the TTLO (time to link opt) from 61s to 9s (on a 3.2ghz P4 Xeon). -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

Nov 19, 2003 To Everyone on this list... What's been suggested for a FAQ and other "much needed information" for such a _HIGHLY_ technical software product has been proven thousands of times in the past few months. Even an untrained monkey can see that, including many geeks. Those that are against it are the very _few_ arrogant self-centered egotistical few that think their middle initials are VoIP. It would be very easy t...

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

...tion than disk-only snapshots (even if --quiesce was used to minimze the need for an fsck on the disk contents). Thus, --memspec snapshots require no guest cooperation, at the expense of requiring more disk space to hold the state. On the other hand, if you are going to do a --memspec snapshot, I _highly_ recommend that you snapshot ALL disks at once, rather than trying to do just one disk at a time. With --disk-only (whether or not you use --quiesce), all you can recover is the disk state by a fresh boot of the disk (--quiesce minimizes the chance that the fresh boot needs an fsck). But with --me...

Hi LLVMers! It's official: LLVM 1.1 is now officially available! I think that everyone who has worked on it is really proud of the high quality of the release. It is faster, more robust, and more featureful than 1.0. If you are currently using LLVM 1.0, I _highly_ recommend upgrading. Huge thanks go out to all those that helped make it possible. You can download it here: http://llvm.cs.uiuc.edu/releases/ A detailed list of the new features and fixed bugs can be found in the 1.1 release notes: http://llvm.cs.uiuc.edu/releases/1.1/docs/ReleaseNotes.html#wh...

Hi, Anyone know anything about Asterisk's support for door phones? Receiving the call from the door intercom system, opening the door, etc? Any hardware recommendations? I understand that the equipment we have now is Panasonic proprietary and came with the currently deployed Panasonic TD12-32 pbx. We intend to deploy Asterisk in a 72 extensions + 16 trunks in a while, so any info will be

...snapshots (even if --quiesce was used to > minimze the need for an fsck on the disk contents). Thus, --memspec > snapshots require no guest cooperation, at the expense of requiring more > disk space to hold the state. On the other hand, if you are going to do > a --memspec snapshot, I _highly_ recommend that you snapshot ALL disks > at once, rather than trying to do just one disk at a time. With > --disk-only (whether or not you use --quiesce), all you can recover is > the disk state by a fresh boot of the disk (--quiesce minimizes the > chance that the fresh boot needs an f...