Re: [RFC 4.8] use ip+cfa to identify unwind frames, if possible

2012-02-17 Thread Richard Henderson
On 02/17/12 09:31, David Daney wrote: > Just off the top of my head (with out actually looking at the code). Is > there anything that could be done with the register zero save slot (if it > even exists)? No. We're talking about saving information in the exception structure between unwindings.

Re: [RFC 4.8] use ip+cfa to identify unwind frames, if possible

2012-02-17 Thread David Daney
On 02/16/2012 03:32 PM, Richard Sandiford wrote: David Daney writes: On 02/16/2012 02:12 PM, Richard Henderson wrote: [...] Thanks for the patch. index 1c19f8b..59d4560 100644 --- a/gcc/config/mips/mips.h +++ b/gcc/config/mips/mips.h @@ -2920,3 +2920,15 @@ extern GTY(()) struct target_globa

Re: [RFC 4.8] use ip+cfa to identify unwind frames, if possible

2012-02-16 Thread Joseph S. Myers
On Thu, 16 Feb 2012, Richard Henderson wrote: > On 02/16/2012 11:54 AM, Richard Henderson wrote: > > I'll work on a proper fix to the unwinder; we can then decide > > whether and when to apply it... > > Something like this. Not the best of solutions, but we've run out > of bits in the exception

Re: [RFC 4.8] use ip+cfa to identify unwind frames, if possible

2012-02-16 Thread Richard Sandiford
David Daney writes: > On 02/16/2012 02:12 PM, Richard Henderson wrote: > [...] Thanks for the patch. >> index 1c19f8b..59d4560 100644 >> --- a/gcc/config/mips/mips.h >> +++ b/gcc/config/mips/mips.h >> @@ -2920,3 +2920,15 @@ extern GTY(()) struct target_globals *mips16_globals; >> with argum

Re: [RFC 4.8] use ip+cfa to identify unwind frames, if possible

2012-02-16 Thread David Daney
On 02/16/2012 02:12 PM, Richard Henderson wrote: [...] index 1c19f8b..59d4560 100644 --- a/gcc/config/mips/mips.h +++ b/gcc/config/mips/mips.h @@ -2920,3 +2920,15 @@ extern GTY(()) struct target_globals *mips16_globals; with arguments ARGS. */ #define PMODE_INSN(NAME, ARGS) \ (Pmode =