Re: [Qemu-devel] [PATCH] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame

On 3/29/16 06:57, Chen Gang wrote: > On 3/29/16 06:17, Laurent Vivier wrote: >> >> The address of retcode in host and guest can differ. >> You need something like: >> >> restorer = (unsigned long)(frame_addr + offsetof(struct >> target_rt_sigframe, retcode)); >> >> I've experienced this on

Re: [Qemu-devel] [PATCH] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame

On 3/29/16 06:17, Laurent Vivier wrote: >> On 3/15/16 05:51, cheng...@emindsoft.com.cn wrote: >>> >>> Original implementation uses do_rt_sigreturn directly in host space, >>> when a guest program is in unwind procedure in guest space, it will get >>> an incorrect restore address, then causes

Re: [Qemu-devel] [PATCH] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame

Le 27/03/2016 11:44, Chen Gang a écrit : > Hello All: > > Please help check this patch when you have time. > > After this patch, we can let gcc testsuite cleanup-10 run successfully. > > Next, I shall continue to implement floating point instructions: remove > (u)int64_to_float64 from fdouble

Re: [Qemu-devel] [PATCH] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame

Hello All: Please help check this patch when you have time. After this patch, we can let gcc testsuite cleanup-10 run successfully. Next, I shall continue to implement floating point instructions: remove (u)int64_to_float64 from fdouble implementation. Thanks. On 3/15/16 05:51,

[Qemu-devel] [PATCH] linux-user/signal.c: Generate opcode data for restorer in setup_rt_frame

From: Chen Gang Original implementation uses do_rt_sigreturn directly in host space, when a guest program is in unwind procedure in guest space, it will get an incorrect restore address, then causes unwind failure. Also cleanup the original incorrect indentation.