Closed robryk closed 8 years ago
Thanks for this report! I experienced almost the same issue when working on an OS X port pull-request yesterday. I have to redesign the stack allocation so that it is always aligned.
It might be worthwhile to do that only when calling a C function (as opposed to one created out of whole cloth by JIT).
On Thu, Sep 17, 2015 at 11:39 AM, mnt.mn notifications@github.com wrote:
Thanks for this report! I experienced almost the same issue when working on an OS X port pull-request yesterday. I have to redesign the stack allocation so that it is always aligned.
— Reply to this email directly or view it on GitHub https://github.com/mntmn/interim/issues/5#issuecomment-141024438.
True, although it concerns only C functions that (somewhere down the line) use 128-bit registers afaik. I think I don't want stack alignment on every alloc_int call, but for example in filesystem calls that interact with the Host OS (in your case, OpenGL).
Fixed in latest commit. Can you confirm this?
Verified at a49f069
Sledge crashes for me when I try to use the framebuffer. I am running on a 64-bit Intel architecture, in a Linux environment. The issue seems to be an unaligned address in a MOVAPS instruction that points to the stack, so I'm pretty sure that the issue is that the call to libsdl has badly aligned stack. See the following gdb session: