On 01/29/2012 07:57 AM, Tom de Vries wrote:
> Richard,
> 
> [now cc-ing gcc-patches]
> 
> this patch fixes PR50283 in a target-independent way.
> 
> it asserts on frame-related insns in the delay slot of insns that can throw,
> and prevents the assert by testing for the same condition in
> eligible_for_{delay,annul_true,annul_false}.
> 
> build and reg-tested on mips64el.
> 
> I don't know of any tests currently failing on this, so I think it's not
> appropriate for stage4. OK for stage1 ?
> 

If we can't tell one unwinder (eh) what to do with this, how do we
expect to be able to tell another unwinder (gdb)?  Thus I'm not sure
how "throwing" has anything to do with it.

I certainly agree that we shouldn't do anything during stage4 unless
we can come up with a wrong-code test case.


r~

Reply via email to