public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jacob dot navia at ants dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/23278] SJLJ-exceptions broken
Date: Sun, 07 Aug 2005 20:30:00 -0000	[thread overview]
Message-ID: <20050807203044.9219.qmail@sourceware.org> (raw)
In-Reply-To: <20050807195054.23278.jacob.navia@ants.com>


------- Additional Comments From jacob dot navia at ants dot com  2005-08-07 20:30 -------
>>Why do the program requires SJLJ exceptions?  That does not make sense.

Yes it does.

The problem is that we are generating dynamically code
using an embedded compiler. Our stack looks like this:

	C++ stack
	dynamically generated code
	C++ stack
	dynamically generated code
	C++ stack <--- makes a throw

If we would use table-driven (dwarf2) exceptions, the program would crash
since there are no dwarf tables for our dynamically generated code!

We HAVE to use sjlj exceptions.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23278


  parent reply	other threads:[~2005-08-07 20:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 19:50 [Bug c++/23278] New: " jacob dot navia at ants dot com
2005-08-07 19:57 ` [Bug libstdc++/23278] " pinskia at gcc dot gnu dot org
2005-08-07 20:30 ` jacob dot navia at ants dot com [this message]
2005-08-07 20:33 ` pinskia at gcc dot gnu dot org
2005-08-07 20:37 ` dberlin at dberlin dot org
2005-08-07 20:37 ` [Bug c++/23278] New: " Daniel Berlin
2005-08-08 18:45 ` [Bug libstdc++/23278] " pinskia at gcc dot gnu dot org
2005-08-09 19:57 ` jacob dot navia at ants dot com
2005-08-09 22:53   ` Daniel Berlin
2005-08-09 22:53 ` dberlin at dberlin dot org
2005-08-15 19:39 ` bkoz at gcc dot gnu dot org
2005-09-12 19:13 ` bkoz at gcc dot gnu dot org
2005-09-12 21:44 ` jacob dot navia at ants dot com
2005-09-13 19:29 ` [Bug c++/23278] " bkoz at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050807203044.9219.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).