| commit | 32cd070c969ffd0b405460ef75f6fa095ed9657e | |
| author | Milutin Jovanović <jovanovic.milutin@gmail.com> | |
| Mon, 11 Jun 2012 00:58:48 +0000 (10 20:58 -0400) | ||
| committer | Milutin Jovanović <jovanovic.milutin@gmail.com> | |
| Mon, 11 Jun 2012 00:58:48 +0000 (10 20:58 -0400) | ||
| tree | bc36b780bef2878e9bdc53c5265f7fa21ffa6eed | treesnapshot (tar.gz zip) |
| parent | a42b029101a758127de570b113767977fbce7b2a | commitdiff |
osx: Removed some optimizations for x86 builds as they were causing seg faults.
When using gcc compiler (as opposed to llvm) to build 32 bit tcc, compiler flags
-mpreferred-stack-boundary=2, -march=i386 and -falign-functions=2 were being
used. -march is redundant as -m32 is already being used. The other two seem to
be corrupting stack. I am not sure why this is the case, as the explanation of
the flags states that only running code size should be affected, but it does.
I think that is is safe to remove these flags altogether for all compilers and
platforms, especially since they are not being used for 64 bit builds. However
I do not want to apply such wide change without agreement from the people on the
mailing list.
When using gcc compiler (as opposed to llvm) to build 32 bit tcc, compiler flags
-mpreferred-stack-boundary=2, -march=i386 and -falign-functions=2 were being
used. -march is redundant as -m32 is already being used. The other two seem to
be corrupting stack. I am not sure why this is the case, as the explanation of
the flags states that only running code size should be affected, but it does.
I think that is is safe to remove these flags altogether for all compilers and
platforms, especially since they are not being used for 64 bit builds. However
I do not want to apply such wide change without agreement from the people on the
mailing list.
| .gitignore | diffblobblamehistory | |
| Makefile | diffblobblamehistory |