public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrey Slepuhin <pooh@msu.ru>
To: Ruslan Shevchenko <Ruslan@Shevchenko.kiev.ua>
Cc: egcs@cygnus.com
Subject: RE: [Fwd: No C/C++ fundamental type 1 error.]
Date: Thu, 05 Feb 1998 04:52:00 -0000	[thread overview]
Message-ID: <XFMail.980205150931.pooh@msu.ru> (raw)
In-Reply-To: <34D85E48.B50D0F09@Shevchenko.kiev.ua>

On 04-Feb-98 Ruslan Shevchenko wrote:
> Anybody know,   Teemu Torma's patch, for generating thread-safe
> exception
> handling code to egcs now intengrated in the main stream.
> 
> (i.e. current egcs from CVS repositary have it ?)

Yes, current development tree containes Teemu's patch, but you
should carefully check if thread-safe versions of libstdc++
and libgcc are generated for your target (otherwise, there is
no much effort to do some tuning of configuration).

Andrey.


  reply	other threads:[~1998-02-05  4:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-05  2:28 Ruslan Shevchenko
1998-02-05  4:52 ` Andrey Slepuhin [this message]
1998-02-05 13:49   ` Ruslan Shevchenko
1998-02-05 12:42 Mike Stump

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=XFMail.980205150931.pooh@msu.ru \
    --to=pooh@msu.ru \
    --cc=Ruslan@Shevchenko.kiev.ua \
    --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).