Message-ID: <4F2958E9.40103@gmail.com>
Date: Wed, 01 Feb 2012 16:23:21 +0100
From: marco atzeri <marco.atzeri@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: llvm/clang 3.0-1 silently ignores C++ exception handling
References: <4F2835F0.5050704@t-online.de> <1328068369.5448.6.camel@YAAKOV04> <4F28D9ED.7040703@t-online.de> <4F29470B.7010109@cs.utoronto.ca>
In-Reply-To: <4F29470B.7010109@cs.utoronto.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 2/1/2012 3:07 PM, Ryan Johnson wrote:

>> OK, I'll do.
>>
>> Must be at least somewhat Cygwin specific. Clang on i686 Linux
>> generates exception handling code properly (tested with clang 2.9 on
>> Debian).
> I have vague memories that Clang doesn't support SJLJ exceptions, and
> further vague memories that Cygwin favors SJLJ because dwarf exceptions
> interact badly with The Windows Way of doing things. That could be your
> problem, assuming my vague memories aren't completely out of date.
>
> Either way, tho, it's a bit strange that the compiler doesn't squawk at
> you. Clang prides itself on having good diagnostics, and it's not
> exactly a small semantic change to silently replace throw with abort().
>
> Ryan

gcc4-4.3 and later use Dwarf instead of SJLJ that was used by gcc-3

Regards
Marco


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