| www.delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY |
| X-Spam-Check-By: | sourceware.org |
| Message-ID: | <4F2C4D31.20602@t-online.de> |
| Date: | Fri, 03 Feb 2012 22:10:09 +0100 |
| From: | Christian Franke <Christian DOT Franke AT t-online DOT de> |
| User-Agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110928 Firefox/7.0.1 SeaMonkey/2.4.1 |
| MIME-Version: | 1.0 |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: llvm/clang 3.0-1 silently ignores C++ exception handling |
| References: | <4F2835F0 DOT 5050704 AT t-online DOT de> <1328068369 DOT 5448 DOT 6 DOT camel AT YAAKOV04> <4F29989B DOT 1020701 AT t-online DOT de> <1328142965 DOT 1328 DOT 4 DOT camel AT YAAKOV04> |
| In-Reply-To: | <1328142965.1328.4.camel@YAAKOV04> |
| X-IsSubscribed: | yes |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| 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 |
Yaakov (Cygwin/X) wrote:
> On Wed, 2012-02-01 at 20:55 +0100, Christian Franke wrote:
>> Yaakov (Cygwin/X) wrote:
>>> On Tue, 2012-01-31 at 19:41 +0100, Christian Franke wrote:
>>>> Clang++ 3.0-1 does not produce any exception handling code. Unwind
>>>> tables and code within catch(.) {...} blocks are not generated. Throw
>>>> always abort()s program.
>>>>
>>>> Is this as excepted?
>>> As best as I can tell, this is an upstream limitation.
>> Yes, http://llvm.org/bugs/show_bug.cgi?id=11285
> Much as I suspected, although you'd think such an unfortunate limitation
> would be documented somewhere.
A probably simple way would be:
- set default to -fno-exceptions,
- print a warning if -fexceptions is specified.
Then compilation fails if exceptions or C++ standard library are used.
Option -fexception could be enabled if exceptions are used only to
handle fatal errors like allocation or assertion failures which is the
case for the standard library.
>
> I honestly don't have the time or expertise to implement this right now,
> so I'm afraid this is an upstream case of PTC.
Yes, see last comment in upstream bug entry.
BTW: Thanks for packaging this!
Christian
--
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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |