From: Andrey Slepuhin <pooh@msu.ru>
To: egcs@cygnus.com
Subject: threads & exception handling
Date: Tue, 25 Nov 1997 02:58:00 -0000 [thread overview]
Message-ID: <347AAF40.E9674E72@msu.ru> (raw)
Hi,
I have many troubles because current exception handling implementation
in
egcs is not thread-safe. Do you plan to solve the problem? It seems to
me that
it is not hard to do this for sjlj exception handling mechanism, but
this may
cause a creation of separate version of libgcc for multithreaded
applications. I can do some hack myself but I don't want to invent the
wheel
if the work already in progress.
Regards,
Andrey.
reply other threads:[~1997-11-25 2:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=347AAF40.E9674E72@msu.ru \
--to=pooh@msu.ru \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).