<div dir="ltr"><div><div><div><div><div class=""><img class="" id=":7nm" src="https://mail.google.com/mail/images/cleardot.gif" alt="">From:</div><a href="http://sourceforge.net/p/fbc/bugs/659/" target="_blank">http://sourceforge.net/p/fbc/bugs/659/</a><br>
<br>"The GCC devs decided to unilaterally change the Linux x86 ABI <span>[1]</span> <span>[2]</span> <span>[3]</span> <span>[4]</span>.
I'm not sure when this happened, but I think it first became a common
problem with GCC 4.1. Previously the Linux x86 ABI was the "SysV i386
ABI", which stated that the stack is aligned to a 4-byte boundary on
function entry. GCC now assumes by default that the stack is aligned to a
16-byte boundary. This is an very controversial issue with the GCC devs
saying they have changed the ABI, and many other people considering the
SysV ABI to be the real ABI and GCC to be buggy. GCC Bugzilla is full
of flamewars. GCC devs have said "GCC chose to change the <em>unwritten</em> standard for the ABI in use for IA32 GNU/Linux" and "The ABI is undocumented; that is reality" <span>[3]"</span><br><br>
</div>basically, it affects everything which dealing with generated code.<br></div>like JIT/FFI.<br><br></div>Now it explains why NB started crashing on never versions of ubuntu,<br></div>while worked well before.<br><br clear="all">
<div><div><div><div><br>-- <br>Best regards,<br>Igor Stasenko.
</div></div></div></div></div>