On Fri, Jul 29, 2011 at 09:16:09AM -0400, David Edelsohn wrote: > Which has the problem? Which are you trying to solve? And how is > your change solving it?
Michael's save_toc_in_prologue emit_frame_save writes unwind info for the wrong frame. That r2 save is the current r2. What we need is info about the previous r2, so we can restore when unwinding. I made a similar mistake in frob_update_context in that the value saved by an indirect function call sequence is the r2 for the current function. I also restored from the wrong location. -- Alan Modra Australia Development Lab, IBM
