public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kaz Kylheku <kaz@cafe.net>
To: "'Bastiaan Bakker'" <Bastiaan.Bakker@Harbinger.nl>,
	"egcs@cygnus.com" <egcs@cygnus.com>
Subject: RE: Exception Handling is thread safe?
Date: Mon, 23 Mar 1998 15:11:00 -0000	[thread overview]
Message-ID: <01BD5640.182BEEF0.kaz@cafe.net> (raw)

On Thursday, March 19, 1998 2:13 AM, Bastiaan Bakker 
[SMTP:Bastiaan.Bakker@Harbinger.nl] wrote:
> Hi ,
>
> On the OmniORB project pages I read  that egcs' exception handling is
> not thread safe but that it can be fixed with a patch from Teemu Torma.

Thread safe exception handling is available in the March 8th snapshot,
which is what I am using right now. Presumably, it has been incorporated
into the 1.0.2 release; I have not yet checked.

In the March 8th (980308) snapshot, you have to manually enable thread-safe
exception handling by editing the 'gthr.h' header file in the 'gcc' 
subdirectory.

At the top, add

	#define _PTHREADS = 1

if you are using POSIX threads. Otherwise #define _DCE_THREADS
or _SOLARIS_THREADS in the same way.

Then remove the 'libgcc2.a' file, and do a make install. Watch for
libgcc.a being built; if it doesn't happen, remove libgcc2.a and try
again.

Once you have everything successfully built and installed, your
libgcc.a now contains undefined symbols referring to the appropriate
threading library, thus you may have to add the appropriate link options
on the compiler command line to compile C++ code that does
exception handling. (On my system, the pthreads API is in
a separate library; I'm using LinuxThreads in conjunction with
libc5.)

This advice may work for 1.0.2; I don't know yet.

Watch out; I tried to ``cheat'' by doing only a ``make libgcc.a''
in the gcc directory and copying the libgcc.a file manually to
its destination. It did not work for some reason that I don't fully
understand. Only a ``make install'' did the right magic.


             reply	other threads:[~1998-03-23 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-23 15:11 Kaz Kylheku [this message]
1998-03-23 16:09 ` Joe Buck
  -- strict thread matches above, loose matches on Subject: below --
1998-03-19 12:55 Bastiaan Bakker
1998-03-22 11:46 ` Jeffrey A Law
1998-03-23 10:41   ` erwin
1998-03-23 16:39   ` Andi Kleen

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=01BD5640.182BEEF0.kaz@cafe.net \
    --to=kaz@cafe.net \
    --cc=Bastiaan.Bakker@Harbinger.nl \
    --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).