Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<41A08876.1050706@x-ray.at>
Date:	Sun, 21 Nov 2004 13:22:14 +0100
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a4) Gecko/20040927
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: g++ 3.4.1
References:	<00c701c4cc08$990fa300$0200a8c0 AT mindcooler> <6 DOT 1 DOT 2 DOT 0 DOT 0 DOT 20041116182733 DOT 02188880 AT imap DOT myrealbox DOT com> <uis84v7x4 DOT fsf AT gnu DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0411171012170 DOT 1017 AT slinky DOT cs DOT nyu DOT edu> <uekisv6d3 DOT fsf AT gnu DOT org> <419B7A15 DOT 1040207 AT x-ray DOT at> <uzn1gtp4w DOT fsf AT gnu DOT org> <419E952E DOT 8090708 AT familiehaase DOT de> <419F06C0 DOT 3020409 AT x-ray DOT at> <419F40B0 DOT 7000501 AT familiehaase DOT de> <419F8BBF DOT 8010904 AT x-ray DOT at> <419FCB4E DOT 70405 AT familiehaase DOT de> <419FEDE7 DOT 9080601 AT familiehaase DOT de>
In-Reply-To:	<419FEDE7.9080601@familiehaase.de>
X-IsSubscribed:	yes

Gerrit P. Haase schrieb:
> Gerrit P. Haase wrote:
>> No, it will be enabled, or better sjlj will not be enabled and the build
>> defaults to dwarf2.
> 
> I was wrong with this statement.
> 
> To clarify this:
> gcc-3.4 has DWARF2 debug informations enabled, but exception handling 
> will stay to be SjLj exceptions and not be DWARF2, because:
> 
> - there are w32api callback problems
> - there is a generic problem with stdcall fuctions and some combinations
>   of -fomit-frame-pointer/-mtune/optimisation levels
> - it is a major ABI change

So the octave folks will need to build their private dwarf2 exception 
gcc until this is fixed. Or stay with the old versions.

Wonder how this will affect postgresql.
I'll report timings, when the new beta5 is out, 1-3 days.
With the older gcc and postgresql I got 50 concurrent connections, with 
latest versions only max 2, which was way too slow. But it could have 
been some other concurrency problem also.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -