http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28145
nightstrike nightstrike at gmail dot com changed:
What|Removed |Added
CC||nightstrike at
--- Comment #19 from jason at gcc dot gnu dot org 2010-07-16 19:21 ---
Created an attachment (id=21227)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21227action=view)
final __forced_unwind patch and fixes applied in 2007, for historical reference
--
--- Comment #16 from hhinnant at apple dot com 2007-04-15 16:13 ---
(In reply to comment #15)
This makes clean up / rethrow during cancellation awkward. Code would have to
check for two (or more) different kinds of cancellation: Am I executing in an
OS thread, or in a thread pool?
--- Comment #17 from jason at redhat dot com 2007-04-15 19:01 ---
Subject: Re: C++ (throw() and catch(...) {/* fall through
*/ } ) and pthread cancellation are incompatible (at least with NPTL)
hhinnant at apple dot com wrote:
This makes clean up / rethrow during cancellation
--- Comment #15 from jason at redhat dot com 2007-04-13 20:13 ---
Subject: Re: C++ (throw() and catch(...) {/* fall through
*/ } ) and pthread cancellation are incompatible (at least with NPTL)
Howard's example seems to me like an argument for not necessarily using
thread
--- Comment #14 from hhinnant at apple dot com 2006-11-01 23:33 ---
So swallowing a cancel-exception (in C++) is sometimes the right thing to do.
Imagine a thread pool executing a queue of tasks. These tasks can well have
handles so that clients can wait/join with results in the
--- Comment #11 from jason at redhat dot com 2006-08-01 07:10 ---
Subject: Re: C++ (throw() and catch(...) {/* fall through
*/ } ) and pthread cancellation are incompatible (at least with NPTL)
drow at gcc dot gnu dot org wrote:
Just making sure I understand - catch (...) { foo();
--- Comment #12 from drow at gcc dot gnu dot org 2006-08-01 13:02 ---
Subject: Re: C++ (throw() and catch(...) {/* fall through */ } ) and pthread
cancellation are incompatible (at least with NPTL)
On Tue, Aug 01, 2006 at 07:10:53AM -, jason at redhat dot com wrote:
[What does
--- Comment #13 from jason at gcc dot gnu dot org 2006-08-01 21:08 ---
Created an attachment (id=11988)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11988action=view)
NPTL patch for sticky cancellation
Revised, tested patch with testcase.
So, there are 3 patches here, which are
--- Comment #6 from jason at gcc dot gnu dot org 2006-07-31 09:38 ---
Created an attachment (id=11978)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11978action=view)
libstdc++ patch to allow catching forced unwind separately
Trying to move this issue forward: here's a libsupc++
--- Comment #7 from jason at gcc dot gnu dot org 2006-07-31 09:40 ---
Created an attachment (id=11979)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11979action=view)
NPTL patch to allow discarding cancellation exception
And here's a completely untested patch to NPTL to implement
--- Comment #8 from jason at gcc dot gnu dot org 2006-08-01 02:13 ---
Created an attachment (id=11985)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11985action=view)
libstdc++ patch to prevent ... from catching forced unwird
Finally, this patch stops ... from catching forced
--- Comment #9 from jason at gcc dot gnu dot org 2006-08-01 02:33 ---
Created an attachment (id=11986)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11986action=view)
revision to forced-lib.patch that also adds __foreign_exception
--
jason at gcc dot gnu dot org changed:
--- Comment #10 from drow at gcc dot gnu dot org 2006-08-01 02:47 ---
Subject: Re: C++ (throw() and catch(...) {/* fall through */ } ) and pthread
cancellation are incompatible (at least with NPTL)
On Tue, Aug 01, 2006 at 02:13:08AM -, jason at gcc dot gnu dot org wrote:
--- Comment #5 from pcarlini at suse dot de 2006-07-07 17:17 ---
(In reply to comment #4)
However, we know that it should be possible to write cancel-safe C++
libraries (including, in particular, libstdc++); otherwise, it's hard to
use C++ in a multi-threaded application. And, we
--- Comment #3 from drow at gcc dot gnu dot org 2006-06-24 02:52 ---
No, that was not the consensus, and I reported this bug specifically because
the coding practices used in libstdc++ cause problems with cancellation...
progress was being made, the last time I read c++-pthreads, but
--- Comment #4 from mark at codesourcery dot com 2006-06-24 04:10 ---
Subject: Re: C++ (throw() and catch(...) {/* fall through
*/ } ) and pthread cancellation are incompatible (at least with NPTL)
drow at gcc dot gnu dot org wrote:
--- Comment #3 from drow at gcc dot gnu dot
17 matches
Mail list logo
