Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: <3F63F915.4090203@cwilson.fastmail.fm>
Date: Sun, 14 Sep 2003 01:13:57 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Danny Smith <danny_r_smith_2001 AT yahoo DOT co DOT nz>
CC: cygwin AT cygwin DOT com
Subject: Re: Available for testing: gcc-3.3.1-1 and gcc-mingw-20030911-1
References: <20030913205923 DOT 16182 DOT qmail AT web21403 DOT mail DOT yahoo DOT com>
In-Reply-To: <20030913205923.16182.qmail@web21403.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Danny Smith wrote:

> gcc 3.2-3 used Dwarf2 exceptions, which worked most of the time. (In fact,
> I don't recall any bug reports at all on cygwin list).  But it didn't work
> with w32api callbacks, nor with some combinations of compiler switches
> (notably -mcpu=i586 or -mno-accumulate-outgoing-args and
> -fomit-frame-pointer).
> 
> cygwin gcc-3.3.1 uses setjmp-longjmp exception mechanism,
> mingw does too and has done since gcc-3.2.1.
> 
> The two undefined references are Dwarf2 specific.  The corresponding
> SjLj symbols are __gxx_personality_sj0 and  __Unwind_SjLj_Resume.

So, just to make sure I understand...

This "problem" only affects C++ code -- and only C++ code which uses 
exceptions.  If a C++ library uses exceptions, it should be recompiled 
with the new compiler.  If a C++ _program_ uses excetions -- or uses a 
(C++) library which uses exceptions -- then it should be 
recompiled/relinked too, but only after the suspect lib has been 
recompiled with gcc-3.3.1, as well.

But C code (libraries, apps, etc) are unaffected, and need no recompiling.

Right?

--
Chuck




--
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/