search for: invokesite

On Thu, Jul 16, 2009 at 9:10 AM, Kenneth Uildriks<kennethuil at gmail.com> wrote: > 1. Which ones?  I know that Windows uses it for the "this" pointer. The internal fastcc convention and the Windows fastcall convention off the top of my head. > Anyway, unless the callee is required to preserve it in a given > calling convention, that doesn't preclude us using it for

1. Which ones? I know that Windows uses it for the "this" pointer. Anyway, unless the callee is required to preserve it in a given calling convention, that doesn't preclude us using it for a *return* value. It would be checked after calls return, and wouldn't affect the use of the register for passing values in before the call is made. The callee would set it right before

...new intrinsic or two. Anyway, here's my new plan: 1. A thread local global variable, type i8*, initialized to zero. 2. At invoke callsites, right before the invoke call a native method (mysetjmp) that: a. Saves ESI, EDI, EBX, EBP, ESP to a buffer alloca'd within the method containing the invokesite.. b. Sets EAX to 0 c. Returns. 3. The return value of that native method (EAX) is checked, and if nonzero, branch to unwind label. Otherwise, save the value of the thread-local-global into the buffer, write the address of that alloca'd buffer into the thread-local global and make the call. 4...