From: "Luke A. Guest" <laguest@archeia.com>
To: GCC ML <gcc@gcc.gnu.org>
Subject: Re: ARM EABI ZCX Ada (4.6.1) almost working
Date: Mon, 10 Oct 2011 08:45:00 -0000 [thread overview]
Message-ID: <1318210137.26212.66.camel@rogue> (raw)
In-Reply-To: <1318189083.26212.64.camel@rogue>
On Sun, 2011-10-09 at 20:38 +0100, Luke A. Guest wrote:
> Anyway, I changed the code to throw an exception in a nested subprogram,
> this was also caught by the outer subprogram. I then added a raise;
> statement as a handler to see if it would reraise and then exit the
> program, sadly, I get an infinite loop in the search phase (export
> EH_DEBUG=1 shows this).
On further thinking about this, I have a feeling this may have something
to do with the Private1 field of the unwind_exception, but I'm not too
sure how yet.
Luke.
next prev parent reply other threads:[~2011-10-10 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 19:43 Help required re ARM EABI ZCX Ada (4.6.1) Luke A. Guest
2011-10-10 5:08 ` ARM EABI ZCX Ada (4.6.1) almost working Luke A. Guest
2011-10-10 8:45 ` Luke A. Guest [this message]
2011-10-12 7:39 ` Eric Botcazou
2011-10-12 8:12 ` Eric Botcazou
2011-10-12 8:17 ` Luke A. Guest
2011-10-12 9:34 ` Eric Botcazou
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=1318210137.26212.66.camel@rogue \
--to=laguest@archeia.com \
--cc=gcc@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).