This is the mail archive of the
ecos-patches@sources.redhat.com
mailing list for the eCos project.
Re: C++ exception handling in multithreaded applications
- From: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- To: Thomas Koeller <thomas dot koeller at baslerweb dot com>
- Cc: ecos-patches at sources dot redhat dot com
- Date: Fri, 14 Nov 2003 12:33:29 +0100
- Subject: Re: C++ exception handling in multithreaded applications
- Organization: Zylin AS
- References: <1068797659.4083.9.camel@famine> <200311141136.15825.thomas.koeller@baslerweb.com>
> Just a thought: I'd expect that there are not all that many applications
> actually using C++ exceptions, and this feature would add an overhead to
> every context switch.
I'm not sure it has to be configurable, because the overhead is truely
minimal. The only code I add to context switch is the code below:
current->entry_point=(cyg_thread_entry*)fc_static;
fc_static=(struct SjLj_Function_Context *)next->entry_point;
I haven't measured how many % overhead this adds to the context switch,
but it wouldn't surprise me if it was <1%.
> OTOH, we should of course strive to support all
> standard language features. So I'd say this option should be configurable
> via cdl (is it? I didn't have the time to look at your patch.).
What I posted was simply my test changes, so no.
Somehow the GCC libraries need to be tweaked:
http://gcc.gnu.org/ml/gcc-patches/2003-07/msg01657.html
Ãyvind