On Tue, 25 Apr 2006 20:53:01 +0300, Avi Kivity said: > Additionally, C++ guarantees that if an exception is thrown after > spin_lock() is called, then the spin_unlock() will also be called. > That's an interesting mechanism by itself. Gaak. So let me get this straight - We lock something, then we hit an exception because something corrupted the lock. Then we *unlock* it so more code can trip over it. Sometimes the correct semantic is to *leave it locked*.
Attachment:
pgpIQLRLj75Xd.pgp
Description: PGP signature
- Follow-Ups:
- Re: Compiling C++ modules
- From: Avi Kivity <[email protected]>
- Re: Compiling C++ modules
- References:
- Compiling C++ modules
- From: Gary Poppitz <[email protected]>
- Re: Compiling C++ modules
- From: Alan Cox <[email protected]>
- Re: Compiling C++ modules
- From: Avi Kivity <[email protected]>
- Re: Compiling C++ modules
- From: Kyle Moffett <[email protected]>
- Re: Compiling C++ modules
- From: Avi Kivity <[email protected]>
- Re: Compiling C++ modules
- From: Kyle Moffett <[email protected]>
- Re: Compiling C++ modules
- From: Avi Kivity <[email protected]>
- Re: Compiling C++ modules
- From: "Dmitry Torokhov" <[email protected]>
- Re: Compiling C++ modules
- From: Avi Kivity <[email protected]>
- Re: Compiling C++ modules
- From: "Dmitry Torokhov" <[email protected]>
- Re: Compiling C++ modules
- From: Avi Kivity <[email protected]>
- Compiling C++ modules
- Prev by Date: RE: [PATCH] Profile likely/unlikely macros
- Next by Date: Re: [stable] 2.6.16.6 breaks java... sort of
- Previous by thread: Re: Compiling C++ modules
- Next by thread: Re: Compiling C++ modules
- Index(es):