Post B6m6wxjbWSqBwMbqAC by moody@hj.9fs.net
 (DIR) More posts by moody@hj.9fs.net
 (DIR) Post #B6m1tIevHh1ruJr0Rk by moody@hj.9fs.net
       1 likes, 0 repeats
       
       flan% cat /dev/osversion && echo && x86_64-9front-plan9-gcc --version2000x86_64-9front-plan9-gcc (GCC) 16.1.0Copyright (C) 2026 Free Software Foundation, Inc.This is free software; see the source for copying conditions.  There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
       
 (DIR) Post #B6m6wxjbWSqBwMbqAC by moody@hj.9fs.net
       0 likes, 0 repeats
       
       And this is about all it can do at the moment, for some reason it seems to be unaligning its own stack and then expecting to SSE to and from it. I tried throwing -mstackrealign just to see if it would figure itself out but that doesn't seem to do anything. I specifically make sure the stack is 16byte aligned in the newlib entrypoint, and I can verify that it starts aligned at function start so I'm thinking this is just a bug. Is this masked on linux? Does it transparently fix sse alignment fuckups? I fought with this more or less all day so forgive me taking the easy way out and asking the void before I take a nice long break from this.