From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24357 invoked by alias); 12 Sep 2005 21:44:46 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 24100 invoked by alias); 12 Sep 2005 21:44:07 -0000 Date: Mon, 12 Sep 2005 21:44:00 -0000 Message-ID: <20050912214407.24099.qmail@sourceware.org> From: "jacob dot navia at ants dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050807195054.23278.jacob.navia@ants.com> References: <20050807195054.23278.jacob.navia@ants.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/23278] SJLJ-exceptions broken X-Bugzilla-Reason: CC X-SW-Source: 2005-09/txt/msg01522.txt.bz2 List-Id: ------- Additional Comments From jacob dot navia at ants dot com 2005-09-12 21:44 ------- Subject: RE: SJLJ-exceptions broken 1) I need to use sjlj exceptions because we dynamically generate code. Since we do not have any means of generating the needed dwarf2 tables dynamically because there is no API to do it, we can ONLY use sjlj exception. All this is explained in a previous message. 2) Our stack configuration looks like this: C++ code --------- dynamically generated code --------- C++ code --------- dynamically generated code --------- C++ code <<<<<----- makes a throw The problem is that since there isn't any dwarf2 info for the dynamically generated code, a throw will crash when done in this configuration. That is why we use that. Not because we are brain dead. Thanks for your very useful comments but... yes, I repeat: Not because we are brain dead but because we *need* to do this. I can't send you any reproducing sources since I would need to send our just in time compiler to you. I use this in a toolchain "that now is mostly frozen" because the "new and improved" toolchain will not compile our source code since the bug PR 23167 still was unsolved last time I checked. jacob -----Original Message----- From: bkoz at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org] Sent: Monday, September 12, 2005 12:14 PM To: Jacob Navia Subject: [Bug libstdc++/23278] SJLJ-exceptions broken ------- Additional Comments From bkoz at gcc dot gnu dot org 2005-09-12 19:13 ------- There are no platform details, no reproducing sources, and all this on a toolchain that is now mostly frozen. In addition, I also cannot tell why dwarf eh is not being used. So, the answer the question, does anybody use SJLJ exceptions on linux is: no, not really. Not unless the target is completely brain dead. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23278