From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Henderson <rth@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
rguenther@suse.de, joseph@codesourcery.com, jason@redhat.com,
java@gcc.gnu.org, ian@airs.com,
Olivier Hainque <hainque@adacore.com>
Subject: Re: [RFC] Centralize knowledge of eh personality routines
Date: Wed, 13 Oct 2010 07:04:00 -0000 [thread overview]
Message-ID: <201010130903.00490.ebotcazou@adacore.com> (raw)
In-Reply-To: <4CB4E841.1090308@redhat.com>
> The driver for this patch is SEH, which will add yet another function
> name variant in each of these places in each front end. While I could
> adjust each language appropriately, it seems to me that it is a bit
> cleaner to centralize this knowledge.
-/* Build a decl for a EH personality function named NAME. */
+/* Build a personality function given a language. LANG is really an
+ enum dwarf_source_language. */
Left-overs from when it was only an integer?
+ case DW_LANG_Ada83:
+ case DW_LANG_Ada95:
+ prefix = "__gnat_eh_personality";
+ /* The GNAT folk did not follow the standard naming format.
+ That can change if we ever have to increment the version. */
+ if (ui == UI_DWARF2 || ui == UI_TARGET)
+ unwind = "";
+ version = "";
+ break;
Let's change that right now, we don't guarantee any ABI compatibility between
different major releases. Olivier, any objections?
--
Eric Botcazou
next prev parent reply other threads:[~2010-10-13 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 22:59 Richard Henderson
2010-10-13 1:11 ` Jason Merrill
2010-10-13 4:58 ` Ian Lance Taylor
2010-10-13 7:04 ` Eric Botcazou [this message]
2010-10-13 7:09 ` Arnaud Charlet
2010-10-13 7:23 ` Olivier Hainque
2010-10-13 8:53 ` Andrew Haley
2010-10-13 14:14 ` Mark Mitchell
2010-10-13 18:07 ` Richard Henderson
2010-10-13 18:12 ` Eric Botcazou
2010-10-13 18:26 ` Richard Henderson
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=201010130903.00490.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=ian@airs.com \
--cc=jason@redhat.com \
--cc=java@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
--cc=rth@redhat.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).