Re: Document about threads

2000-08-25 Thread Max Khon
hi, there! On Fri, 25 Aug 2000, Alexander N. Kabaev wrote: > There was a bug in -fsjlj-exceptions code generation related to shared > libraries and to best of my knowledge the correct fix has been imported into > the official gcc CVS tree and was merged into FreeBSD some time ago. Are there > a

Re: Document about threads

2000-08-25 Thread Greg Thompson
>From: "Bryan K. Ogawa" <[EMAIL PROTECTED]> > >If anyone who knows about the state of the FreeBSD threads implementation >could go through it and check it for factual errors, missing bits, etc. >then that would be great. in your section about common reentrant extensions, you mention the IPv6 api

Re: Document about threads

2000-08-25 Thread Alexander N. Kabaev
> this issue is unrelated to threads. FreeBSD stock g++ 2.95.2 compiler > uses -fsjlj-exceptions mechanism for exception handling which is broken > (g++ sometimes generates incorrect code even without any optimization > options given). It is not FreeBSD-specific behaviour. gcc GNATS has > bug repo

Re: Document about threads

2000-08-25 Thread Max Khon
hi, there! On Fri, 25 Aug 2000, Bryan K. Ogawa wrote: > 1. I had seen an email in the mailing list archives which asserted that > C++ exceptions have been broken since August 1999 in the multithread case > -- does anyone know what the status in 4.1-STABLE and -CURRENT are? I've > managed to ge

Document about threads

2000-08-25 Thread Bryan K. Ogawa
Hey all, I have been trying to port some code to FreeBSD which currently runs under Linux (and to some degree, Solaris). Since I'm a longtime FreeBSD user, I'm pretty excited to get a chance to port to FreeBSD. The program I'm working on uses both POSIX threads and ISO C++ (including templates