;> Subject: Re: [PATCH][PR target/84066] Wrong shadow stack register size is
>> saved for x32
>>
>> On Tue, Jan 30, 2018 at 6:38 AM, Uros Bizjak wrote:
>> > On Tue, Jan 30, 2018 at 3:19 PM, Tsimbalist, Igor V
>> > wrote:
>> >> x32 is a 64-bit proce
> -Original Message-
> From: H.J. Lu [mailto:hjl.to...@gmail.com]
> Sent: Tuesday, January 30, 2018 3:45 PM
> To: Uros Bizjak
> Cc: Tsimbalist, Igor V ; gcc-
> patc...@gcc.gnu.org
> Subject: Re: [PATCH][PR target/84066] Wrong shadow stack register size is
> saved
On Tue, Jan 30, 2018 at 6:38 AM, Uros Bizjak wrote:
> On Tue, Jan 30, 2018 at 3:19 PM, Tsimbalist, Igor V
> wrote:
>> x32 is a 64-bit process with 32-bit software pointer and kernel may
>> place x32 shadow stack above 4GB. We need to save and restore 64-bit
>> shadow stack register for x32. buil
On Tue, Jan 30, 2018 at 3:19 PM, Tsimbalist, Igor V
wrote:
> x32 is a 64-bit process with 32-bit software pointer and kernel may
> place x32 shadow stack above 4GB. We need to save and restore 64-bit
> shadow stack register for x32. builtin jmp buf size is 5 pointers. We
> have space to save 64-
x32 is a 64-bit process with 32-bit software pointer and kernel may
place x32 shadow stack above 4GB. We need to save and restore 64-bit
shadow stack register for x32. builtin jmp buf size is 5 pointers. We
have space to save 64-bit shadow stack pointer: 32-bit SP, 32-bit FP,
32-bit IP, 64-bit SS
