tinycc/.gitignore

*.o
*.a
tcc_g
tcc
tc2.c
doc
tc3s.c
p3.c
tc1.c
error.c
i386-gen1.c
test.out2
test.out3
web.sh
memdebug.c
bench
Makefile.uClibc
boundtest
prog.ref
test.ref
test.out
tcc-doc.html
ideas
tcctest.ref
linux.tcc
ldtest
libtcc_test
instr.S
p.c
p2.c
tcctest[1234]
test[1234].out
tests/tcclib.h
tests/tcctest.gcc
.gdb_history
tcc.1
tcc.pod
config.h
config.mak
config.texi
tags
.DS_Store
*.swp
lib/x86_64
lib/i386
tcc-doc.info
conftest*
tiny_libmaker
*.dSYM
.gitignore += .o .a Ignores libtcc.o, libtcc.a and a bunch of other files (see previous patch for details) 2010-06-12 22:26:37 +08:00			`*.o`
			`*.a`
added cvsignore 2002-08-18 21:27:16 +08:00			`tcc_g`
			`tcc`
			`tc2.c`
			`doc`
			`tc3s.c`
			`p3.c`
			`tc1.c`
			`error.c`
			`i386-gen1.c`
			`test.out2`
			`test.out3`
			`web.sh`
			`memdebug.c`
			`bench`
			`Makefile.uClibc`
			`boundtest`
			`prog.ref`
			`test.ref`
			`test.out`
			`tcc-doc.html`
			`ideas`
			`tcctest.ref`
			`linux.tcc`
			`ldtest`
			`libtcc_test`
updated 2002-08-18 22:34:02 +08:00			`instr.S`
			`p.c`
			`p2.c`
			`tcctest[1234]`
			`test[1234].out`
Further changes improving the OSX build. Everything builds. libtest passes. Other tests still have issues, currently with weak linking. One of the primary stumbling blocks on OSX is the lack of support for mach-o binaries. Therefore all tcc usage on OSX has to be limited to elf binaries, presumably produced by tcc itself. Therefore I had to enable building of tiny_libmaker for OSX. Then changed the make to use tcc and tiny_libmaker to compile the tcclib1. In order to compile the tests, specifically the parts that use weak linking, I have had to define MACOSX_DEPLOYMENT_TARGET to 10.2, which seems like a hack, but extensive searching seems to indicate that this is the only way to make apple gcc allow weak linking. Using any other value, bigger or smaller breaks weak linking. Also added _ANSI_SOURCE define required by some OSX headers, and some cosmetic gitignore changes. I believe these changes should not impact other platforms. 2012-03-07 02:26:36 +08:00			`tests/tcclib.h`
			`tests/tcctest.gcc`
changed license to LGPL 2003-05-24 22:18:56 +08:00			`.gdb_history`
			`tcc.1`
			`tcc.pod`
			`config.h`
			`config.mak`
			`config.texi`
.gitignore += tags 2010-06-21 00:48:16 +08:00			`tags`
Patch attempting to build OSX TinyCC. Applied patch found on stackoverflow (link below). I also found some related changes that looked like logically needed. The stackoverflow changes addressed only two registers which were breaking a compile. However reading the code in the same file shows two other register accesses that, while not breaking the build, should have the same fix. http://stackoverflow.com/questions/3712902/problems-compiling-tcc-on-os-x/3713144#3713144 The test driver was changed by changing 'cp -u' into 'cp' as '-u' is not supported on mac osx. I found that osx build required the WITHOUT_LIBTCC define. I suspect the reason for this is tcc unability to handle mach-o files. In order to properly address this I had to change 'configure' to propagate target os name to Makefile. Current state is that simple tests work, but not the whole 'make test' suite runs. To the best of my knowledge, these changes should not impact other platforms. 2012-02-10 01:53:17 +08:00			`.DS_Store`
			`*.swp`
			`lib/x86_64`
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. 2012-06-11 08:58:48 +08:00			`lib/i386`
Patch attempting to build OSX TinyCC. Applied patch found on stackoverflow (link below). I also found some related changes that looked like logically needed. The stackoverflow changes addressed only two registers which were breaking a compile. However reading the code in the same file shows two other register accesses that, while not breaking the build, should have the same fix. http://stackoverflow.com/questions/3712902/problems-compiling-tcc-on-os-x/3713144#3713144 The test driver was changed by changing 'cp -u' into 'cp' as '-u' is not supported on mac osx. I found that osx build required the WITHOUT_LIBTCC define. I suspect the reason for this is tcc unability to handle mach-o files. In order to properly address this I had to change 'configure' to propagate target os name to Makefile. Current state is that simple tests work, but not the whole 'make test' suite runs. To the best of my knowledge, these changes should not impact other platforms. 2012-02-10 01:53:17 +08:00			`tcc-doc.info`
			`conftest*`
Further changes improving the OSX build. Everything builds. libtest passes. Other tests still have issues, currently with weak linking. One of the primary stumbling blocks on OSX is the lack of support for mach-o binaries. Therefore all tcc usage on OSX has to be limited to elf binaries, presumably produced by tcc itself. Therefore I had to enable building of tiny_libmaker for OSX. Then changed the make to use tcc and tiny_libmaker to compile the tcclib1. In order to compile the tests, specifically the parts that use weak linking, I have had to define MACOSX_DEPLOYMENT_TARGET to 10.2, which seems like a hack, but extensive searching seems to indicate that this is the only way to make apple gcc allow weak linking. Using any other value, bigger or smaller breaks weak linking. Also added _ANSI_SOURCE define required by some OSX headers, and some cosmetic gitignore changes. I believe these changes should not impact other platforms. 2012-03-07 02:26:36 +08:00			`tiny_libmaker`
			`*.dSYM`