From: Mikael Pettersson <mikpe@it.uu.se>
To: laurent@guerby.net
Cc: Richard Earnshaw <rearnsha@arm.com>,
aph@redhat.com, Julian Brown <julian@codesourcery.com>,
Arnaud Charlet <charlet@adacore.com>,
gcc-patches@gcc.gnu.org, Matthias Klose <doko@debian.org>,
Martin Guy <martinwguy@gmail.com>,
Joel Sherrill <joel.sherrill@oarcorp.com>,
Ludovic Brenta <ludovic@ludovic-brenta.org>,
Geert Bosch <bosch@adacore.com>,
Olivier Hainque <hainque@adacore.com>,
Mikael Pettersson <mikpe@it.uu.se>,
Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: [PATCH][Ada] arm-linux sjlj port
Date: Mon, 07 Sep 2009 11:31:00 -0000 [thread overview]
Message-ID: <19108.61188.689111.806413@pilspetsen.it.uu.se> (raw)
In-Reply-To: <1252320407.5049.1775.camel@localhost>
Laurent GUERBY writes:
> > Although this patch is completely in the Ada backend, and thus has very
> > little to do with the ARM port maintenance, I'm concerned that we are
> > trying to create an SJLJ port of GCC for ARM linux. Why is that needed?
> > Why aren't we using the unwind tables?
> >
> > Having an SJLJ port (in addition to being very poor performance) seems
> > the wrong way to go to me, as it will just cause confusion for our
> > users.
>
> A non-SJLJ (ZCX in Ada terminology) port would need someone writting the
> personality routine for Ada, that is to say add some stuff in
> gcc/ada/raise-gcc.c for arm EABI. I might get enough time in the future
> to try to do so but I've zero experience in this area (both on the Ada
> side and on the EH side) so even if the patch will likely end up
> trivial it will take me a long while to figure it out.
I had a look last week at gcc's EH handling. For c++, java, and obj-c
the ARM EABI support looks pretty much the same, and while not small
(much #ifdef code) does look simple enough. The Ada EH code looks
entirely different and frankly I have absolutely no clue where or how
to modify it for ARM EABI.
So right now we have a choice of (a) no Ada for ARM EABI, or (b)
an SJLJ Ada for ARM EABI. With (b) we at least have a working and
testable system until someone can work out the ZCX EH details.
/Mikael
next prev parent reply other threads:[~2009-09-07 11:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A82D295.4030907@oarcorp.com>
[not found] ` <56d259a00908121407h19820522y850231afa937ed3a@mail.gmail.com>
[not found] ` <4A832F30.3000708@debian.org>
[not found] ` <19081.10792.105185.512212@pilspetsen.it.uu.se>
[not found] ` <1250976793.17842.404.camel@localhost>
[not found] ` <1251517614.5049.91.camel@localhost>
[not found] ` <19097.768.413069.836610@pilspetsen.it.uu.se>
[not found] ` <19099.37987.927752.847987@pilspetsen.it.uu.se>
2009-09-07 10:25 ` Laurent GUERBY
2009-09-07 10:35 ` Richard Earnshaw
2009-09-07 10:40 ` Arnaud Charlet
2009-09-07 10:45 ` Richard Earnshaw
2009-09-07 10:52 ` Laurent GUERBY
2009-09-07 10:54 ` Arnaud Charlet
2009-09-07 10:47 ` Laurent GUERBY
2009-09-07 11:31 ` Mikael Pettersson [this message]
2009-09-07 12:21 ` Richard Earnshaw
2009-09-07 13:19 ` Mikael Pettersson
2009-09-07 13:28 ` Richard Earnshaw
2009-09-07 14:12 ` Laurent GUERBY
2009-09-07 14:29 ` Andrew Haley
2009-09-07 11:14 ` Eric Botcazou
2009-09-07 12:20 ` Richard Earnshaw
2009-09-07 15:16 ` Eric Botcazou
2009-09-07 13:39 ` Joel Sherrill
2009-09-09 23:05 ` Laurent GUERBY
2009-09-10 7:03 ` 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=19108.61188.689111.806413@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=aph@redhat.com \
--cc=bosch@adacore.com \
--cc=charlet@adacore.com \
--cc=doko@debian.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=joel.sherrill@oarcorp.com \
--cc=julian@codesourcery.com \
--cc=laurent@guerby.net \
--cc=ludovic@ludovic-brenta.org \
--cc=martinwguy@gmail.com \
--cc=rearnsha@arm.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).