This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Persistent IA64 (and others?) exception failure
- From: "Boehm, Hans" <hans_boehm at hp dot com>
- To: "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Cc: "'rth at redhat dot com'" <rth at redhat dot com>, "'tromey at redhat dot com'" <tromey at redhat dot com>, "MOSBERGER, DAVID (HP-PaloAlto,unix3)" <davidm at hpl dot hp dot com>
- Date: Thu, 14 Mar 2002 09:55:14 -0800
- Subject: Persistent IA64 (and others?) exception failure
The gcc back end still occasionally optimizes away saving of the return
address at function calls that are known not to return, e.g. because they
always raise an exception. This was first pointed out a long time ago
(http://gcc.gnu.org/ml/gcc/2001-11/msg00960.html). Richard Henderson
suggested a better approach
(http://gcc.gnu.org/ml/gcc/2001-11/msg01290.html). But at least as of a
couple of days ago, this was still broken in 3.1.
I believe this affects both C++ and Java. I'm not sure whether it affects
platforms other than Itanium.
Is someone working on this? I have been getting good results with the
original patch (http://gcc.gnu.org/ml/gcc/2001-11/msg00960.html) on Itanium
and X86 Linux. (I doubt it has any effect on X86.) Is that patch correct?
If so, can I check it into 3.1 until we get something better?
Hans