search for: ucontext_t

...initial stack pointer when creating the context, and keep track of > it from there.  If we don't actually need to interoperate with > contexts created from the C routines, we have a lot more freedom. I guess the reason to interoperate with contexts from the C routines would be to support ucontext_t's passed into signal handlers? But then the LLVM intrinsics need to specify that their context's layout is the same as ucontext_t's, on platforms where ucontext_t exists. > Anyway, one approach would be to expose intrinsics to interrogate an > inactive context, to get its initial...

Having read through Stackless Python's web pages a bit: 1. They're doing pretty much what I'd like to do, except that I don't want to be tied to a particular language and I'd like to be able to use the stack. (Also, stack use is inescapable with LLVM, as far as I can tell). 2. We should be able to support "hard switching" in Stackless Python by adding a

On the other hand, stack manipulation really ought to be handled by the target, since only the target knows the details of how the stack is laid out to begin with. Also, if we have stack manipulation calls in the IR, optimization quickly becomes very difficult. Unless we just allow optimizers to ignore the stack manipulations and assume they're doing the "right" thing. On the

...ntext, and keep track of >>> it from there.  If we don't actually need to interoperate with >>> contexts created from the C routines, we have a lot more freedom. >> >> I guess the reason to interoperate with contexts from the C routines >> would be to support ucontext_t's passed into signal handlers? But then >> the LLVM intrinsics need to specify that their context's layout is the >> same as ucontext_t's, on platforms where ucontext_t exists. > > Or perhaps it can be an argument to the target code generator, if > there's any n...

.../asan/asan_linux.cc b/lib/asan/asan_linux.cc index 845493d..417ecad 100644 --- a/lib/asan/asan_linux.cc +++ b/lib/asan/asan_linux.cc @@ -88,6 +88,11 @@ void GetPcSpBp(void *context, uptr *pc, uptr *sp, uptr *bp) { stk_ptr = (uptr *) *sp; *bp = stk_ptr[15]; # endif +#elif defined(__mips__) + ucontext_t *ucontext = (ucontext_t*)context; + *pc = ucontext->uc_mcontext.gregs[31]; + *bp = ucontext->uc_mcontext.gregs[30]; + *sp = ucontext->uc_mcontext.gregs[29]; #else # error "Unsupported arch" #endif -- 1.7.9.5

...when creating the context, and keep track of >> it from there.  If we don't actually need to interoperate with >> contexts created from the C routines, we have a lot more freedom. > > I guess the reason to interoperate with contexts from the C routines > would be to support ucontext_t's passed into signal handlers? But then > the LLVM intrinsics need to specify that their context's layout is the > same as ucontext_t's, on platforms where ucontext_t exists. Or perhaps it can be an argument to the target code generator, if there's any need to switch "co...

...g syntax to access array members. ntdll: Use a custom signal restorer for Android. riched20/tests: Fix test on 64-bit. configure: Improve the check for the resolver library. configure: Add a check for sys/ucontext.h and include it where appropriate. ntdll: Directly use ucontext_t instead of SIGCONTEXT on all platforms. ntdll: Use the standard mcontext_t type for the signal context on Android. libwine: Update LD_LIBRARY_PATH in the current process from the JNI environment. libwine: No longer look for libraries in the dll path on Android. vnbt.vxd: Inc...

...: ok Checking for socketpair : ok Checking for variable IPV6_V6ONLY : ok Checking for header net/if.h : yes Checking for HAVE_IPV6 : ok Checking whether we have ucontext_t : ok Checking for __sync_fetch_and_add compiler builtin : ok Checking for atomic_add_32 compiler builtin : not found Checking for fallthrough attribute : not found Checking for strdup...