This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Remaining Itanium exception, static linking patches
- From: Andrew Haley <aph at cambridge dot redhat dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'java-patches at gcc dot gnu dot org'" <java-patches at gcc dot gnu dot org>,"'tromey at redhat dot com'" <tromey at redhat dot com>
- Date: Thu, 14 Mar 2002 19:00:13 +0000 (GMT)
- Subject: Remaining Itanium exception, static linking patches
- References: <40700B4C02ABD5119F000090278766443BF08F@hplex1.hpl.hp.com>
Boehm, Hans writes:
> I already posted two messages about Itanium exception handling issues that
> also affect C++ (http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00806.html and
> http://gcc.gnu.org/ml/gcc/2002-03/msg00683.html ) This is a list of the
> remaining (short) ones I have been using to compile SPECjbb. I think the
> first two originally came from Andrew Haley.
>
> The first one turns on dwarf2-exception-style signal handling for IA64. The
> file naming here is probably suboptimal, since IA64 uses unwind information
> separate from the debugging information, and thus AFAICT, there is actually
> no relation to dwarf2. But other than that this one should be
> uncontroversial. I would like to check it in as is, into both the trunk and
> branch.
There's one part of my patch that is evil in that it calls an internal
glibc function. The intention is to call the kernel directly to
install the SEGV handler, rather than through glibc's wrapper. [This
is necessary because we can't unwind through glib'c signal handler
wrapper.] This internal glibc function might change or go away, and
therefore calling it is the wrong thing to do. I should fix this
patch to use the proper syscall interface.
What is your kernel/glibc configuration?
Andrew.