Bug#948396: New glibc broke existing app due to historic stack alignment

2020-01-14 Thread Florian Weimer
* Petr Vandrovec: > Florian Weimer wrote on 1/7/2020 9:31 PM: >> * Petr Vandrovec: >> >>> As far as I can tell, while x86-64 ABI requires stack to be aligned >>> on entry to the functions, x86 ABI does not have any such >>> requirement, and so glibc should align stack itself if it wants to >>>

Bug#948396: New glibc broke existing app due to historic stack alignment

2020-01-08 Thread Petr Vandrovec
Florian Weimer wrote on 1/7/2020 9:31 PM: * Petr Vandrovec: As far as I can tell, while x86-64 ABI requires stack to be aligned on entry to the functions, x86 ABI does not have any such requirement, and so glibc should align stack itself if it wants to use XMM instructions that require aligned

Bug#948396: New glibc broke existing app due to historic stack alignment

2020-01-07 Thread Florian Weimer
* Petr Vandrovec: > As far as I can tell, while x86-64 ABI requires stack to be aligned > on entry to the functions, x86 ABI does not have any such > requirement, and so glibc should align stack itself if it wants to > use XMM instructions that require aligned values. The i386 ABI was changed

Bug#948396: New glibc broke existing app due to historic stack alignment

2020-01-07 Thread Petr Vandrovec
Package: libc6-i386 Version: 2.29-8 Since updating my system today our build system binaries started crashing. Upon further investigation problem is that __mktime_internal code in libc6-i386 now started using 'movaps' instruction without aligning stack on 16 byte boundary. As far as I can tell,