[9fans] venti backup
Hello, I've backed up all my *active* arenas in to another disk, just to be safe. The man page says that the index and the bloom filter may be rebuilt if lost. So it seems sufficient to backup my arenas, am I right? saludos, -- Hugo
Re: [9fans] venti backup
So it seems sufficient to backup my arenas, am I right? Yes, exactly, I haev done this several times. It might take a few hours and some studying of manuals but the arenas are all you need. -Steve
Re: [9fans] venti backup
I've backed up all my *active* arenas in to another disk, just to be safe. The man page says that the index and the bloom filter may be rebuilt if lost. So it seems sufficient to backup my arenas, am I right? Yes, you can rebuild the index and the Bloom filter with 'venti/buildindex -b'. -- David du Colombier
Re: [9fans] venti backup
Great. Thanks. I hope I will never need to use my backed up arenas :-) 2012/1/17 Steve Simon st...@quintile.net: So it seems sufficient to backup my arenas, am I right? Yes, exactly, I haev done this several times. It might take a few hours and some studying of manuals but the arenas are all you need. -Steve -- Hugo
Re: [9fans] assembly syntax in plan 9
On Mon, Jan 16, 2012 at 2:03 PM, Bakul Shah ba...@bitblocks.com wrote: How do you deal with longjmp? I don't have it in front of me, but I do seem to recall the Standard allows that the VLA might still be around though, believe it has an example with said, for better or worse... Anyway, at some point we're able to detect that the previous VLA(s) is no longer active and toss them. On Jan 16, 2012, at 10:51 AM, Comeau At9Fans comeauat9f...@gmail.com wrote: On Mon, Jan 16, 2012 at 10:41 AM, Bakul Shah ba...@bitblocks.com wrote: A frame pointer is needed for C99's variable length arrays but not otherwise. Only an issue if ever plan9 C is extended to handle C99 or C1x. gcc has to do the right thing even with -fno-frame-pointer. What we do in problematic cases with Comeau is to generate code to arrange for the allocation of the VLA on the heap. I'm not saying this is perfect, but at least it gets the feature implementable and up and running as a portable implementation versus perhaps not being able to implement it at all on some platforms. -- Greg Comeau / 4.3.10.1 with C++0xisms now in beta! Comeau C/C++ ONLINE == http://www.comeaucomputing.com/tryitout World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90. Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
Re: [9fans] assembly syntax in plan 9
We do allow VLAs in C++ mode as well, but currently keep them separate from EH. On Mon, Jan 16, 2012 at 2:39 PM, Charles Forsyth charles.fors...@gmail.comwrote: They are compiling C++ which has language-visible exception handling instead. On 16 January 2012 19:03, Bakul Shah ba...@bitblocks.com wrote: How do you deal with longjmp? On Jan 16, 2012, at 10:51 AM, Comeau At9Fans comeauat9f...@gmail.com wrote: On Mon, Jan 16, 2012 at 10:41 AM, Bakul Shah ba...@bitblocks.com wrote: A frame pointer is needed for C99's variable length arrays but not otherwise. Only an issue if ever plan9 C is extended to handle C99 or C1x. gcc has to do the right thing even with -fno-frame-pointer. What we do in problematic cases with Comeau is to generate code to arrange for the allocation of the VLA on the heap. I'm not saying this is perfect, but at least it gets the feature implementable and up and running as a portable implementation versus perhaps not being able to implement it at all on some platforms. -- Greg Comeau / 4.3.10.1 with C++0xisms now in beta! Comeau C/C++ ONLINE == http://www.comeaucomputing.com/tryitout World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90. Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
Re: [9fans] assembly syntax in plan 9
On Mon, Jan 16, 2012 at 2:49 PM, erik quanstrom quans...@quanstro.netwrote: On Mon Jan 16 14:40:41 EST 2012, charles.fors...@gmail.com wrote: They are compiling C++ which has language-visible exception handling instead. On 16 January 2012 19:03, Bakul Shah ba...@bitblocks.com wrote: How do you deal with longjmp? i thought this wasn't entirely supported, see the limitations section. http://drdobbs.com/184401468 (i had a better reference, but can't find it anymore.) My recollection is that that paragraph correctly reflects the situation. -- Greg Comeau / 4.3.10.1 with C++0xisms now in beta! Comeau C/C++ ONLINE == http://www.comeaucomputing.com/tryitout World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90. Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
Re: [9fans] assembly syntax in plan 9
On Mon, Jan 16, 2012 at 3:11 PM, Joel C. Salomon joelcsalo...@gmail.comwrote: On 01/16/2012 02:03 PM, Bakul Shah wrote: On Jan 16, 2012, at 10:51 AM, Greg Comeau comeauat9f...@gmail.com wrote: What we do in problematic cases with Comeau is to generate code to arrange for the allocation of the VLA on the heap. I'm not saying this is perfect, but at least it gets the feature implementable and up and running as a portable implementation versus perhaps not being able to implement it at all on some platforms. How do you deal with longjmp? I recall reading the source for a (mostly-) portable alloca() that checked where on the call-stack is was invoked from and released memory for any alloca() invocation from lower on the stack. (The allocations themselves were on the heap.) We do some analogous book keeping as well. -- Greg Comeau / 4.3.10.1 with C++0xisms now in beta! Comeau C/C++ ONLINE == http://www.comeaucomputing.com/tryitout World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90. Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
Re: [9fans] Rising intonation.
Don't worry cuzz, he's a Bwit. Sweet as, bro. Welease Wodger!
