This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[RFC] Centralize knowledge of eh personality routines

From: Richard Henderson <rth at redhat dot com>
To: GCC Patches <gcc-patches at gcc dot gnu dot org>
Cc: rguenther at suse dot de, joseph at codesourcery dot com, jason at redhat dot com, java at gcc dot gnu dot org, ian at airs dot com, ebotcazou at libertysurf dot fr
Date: Tue, 12 Oct 2010 15:59:13 -0700
Subject: [RFC] Centralize knowledge of eh personality routines

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.

The next possibly objectionable point is including dwarf2.h in tree.h.
I went ahead and did this because in the past we had talked about using
the dwarf language enum in LTO.  I could see eliminating the hackish
language_string -> enum mapping that is done in dwarf2out.c as well.

Comments?  Objections?


r~

Attachment: d-per-1
Description: Text document

Follow-Ups:
- Re: [RFC] Centralize knowledge of eh personality routines
  - From: Jason Merrill
- Re: [RFC] Centralize knowledge of eh personality routines
  - From: Ian Lance Taylor
- Re: [RFC] Centralize knowledge of eh personality routines
  - From: Eric Botcazou
- Re: [RFC] Centralize knowledge of eh personality routines
  - From: Andrew Haley
- Re: [RFC] Centralize knowledge of eh personality routines
  - From: Mark Mitchell
- Re: [RFC] Centralize knowledge of eh personality routines
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]