This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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]

Re: [3.3/3.4/4.0/4.1] IA-64 FP register file corruption on unwind

From: James E Wilson <wilson at specifixinc dot com>
To: Geert Bosch <bosch at adacore dot com>
Cc: gcc-patches at gcc dot gnu dot org,Gabriel Dos Reis <gdr at integrable-solutions dot net>,mark at codesourcery dot com
Date: Tue, 05 Apr 2005 11:19:37 -0700
Subject: Re: [3.3/3.4/4.0/4.1] IA-64 FP register file corruption on unwind
References: <1112676190.10291.44.camel@aretha.corp.specifixinc.com> <bf89c419b1210b5ea6a91f09c932e4de@adacore.com>

On Tue, 2005-04-05 at 07:27, Geert Bosch wrote:
> I'm really amazed nobody ran into this before. Apparently very little
> existing code actually uses exceptions.

You have to have about 18 or so FP variables live at the point where the
exception is thrown and caught, or else you won't be able to see the
breakage.  There is a lot of code using exceptions, but there is
probably very little heavy FP code using exceptions.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Follow-Ups:
- Re: [3.3/3.4/4.0/4.1] IA-64 FP register file corruption on unwind
  - From: Geert Bosch

References:
- [3.3/3.4/4.0/4.1] IA-64 FP register file corruption on unwind
  - From: James E Wilson
- Re: [3.3/3.4/4.0/4.1] IA-64 FP register file corruption on unwind
  - From: Geert Bosch

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