For some reason when using -mpreferred-stack-boundary=2 causes this problem.
Any way, my questions really is this, do we need this whole section at all? The stack-boundary is already not optimized on 64 bit builds. Is tcc being used in environments where this will make a difference? I think this actually slows down the code, but...
Aligning functions? Pretty much the same question. This cannot save more then a few bytes.
-march=i386, -m386? I think that -m32, which is applied later in the makefile, already does when we really need. Are we trying to produce tcc that can run on really old machines?
For now I have disabled this block for osx builds. Can we remove completely? Your thoughts?
[Prev in Thread]
[Next in Thread]
[Tinycc-devel] x86 optimization flags,