Bug#943425: Debian #943425: [s390x] setjmp/longjmp do not save/restore all registers in use

2021-05-05 Thread Andreas Krebbel
On 5/5/21 4:45 AM, Thorsten Glaser wrote: > Dixi quod… > >> Jessica Clarke brought out docs saying f8‥f15 must be saved, the >> other FPU registers not: I can confirm this. It is f8-f15 for the z/Architecture (64 bit). It is f1, f3, f5, f7 for the ESA architecture (32 bit) which is still

Bug#943425: Debian #943425: [s390x] setjmp/longjmp do not save/restore all registers in use

2021-05-04 Thread Thorsten Glaser
Dixi quod… >Jessica Clarke brought out docs saying f8‥f15 must be saved, the >other FPU registers not: This needs to be fixed in klibc. >>• klibc does not really support the FPU anyway > >… GCC chooses to allocate an FPU register for a pointer value. This is a curiosity. >>• the half of v10

Bug#943425: Debian #943425: [s390x] setjmp/longjmp do not save/restore all registers in use (was Use of $v10 register (was Re: klibc: [s390x] SIGSEGV in mksh testcase funsub-2))

2021-05-03 Thread Thorsten Glaser
Dixi quod… >So, setjmp/longjmp in klibc save f1/f3/f5/f7 (as shown on Wikipedia >https://en.wikipedia.org/wiki/Calling_convention#IBM_System/360_and_successors >“the z/Architecture ABI,[11] used in Linux” a page down), while >glibc’s save f8–f15 instead. Jessica Clarke brought out docs saying