From: Eric Botcazou <ebotcazou@adacore.com>
To: "Luke A. Guest" <laguest@archeia.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ARM EABI ZCX Ada (4.6.1) almost working
Date: Wed, 12 Oct 2011 09:34:00 -0000 [thread overview]
Message-ID: <201110120935.35511.ebotcazou@adacore.com> (raw)
In-Reply-To: <1318404120.4680.0.camel@rogue>
> Aye, then the Ada side doesn't build. Can you see what it is I'm
> missing?
You need to further adjust the Ada code (a-exexpr-gcc.adb), which is written
for DWARF EH. In particular, you need to rewrite Propagate_Exception to build
a proper exception for ARM EH.
> I'm beginning to think the whole of a-exexpr-gcc needs to be extracted
> into 2 distinct files, a-exexpr-gcc (normal GCC EH - as it is) and
> a-exexpr-gcc-arm (ARM EABI EH).
Probably some parts of it, yes.
--
Eric Botcazou
prev parent reply other threads:[~2011-10-12 7:39 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
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 [this message]
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=201110120935.35511.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=laguest@archeia.com \
/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).