tinycc/tcctest.c, branch main

new subdirs: include, lib, tests

2009-04-18T13:08:03Z

mute strange difference in tcctest

2009-04-18T13:08:03Z

x86-64: Fix cast from integers to pointers.

2009-04-18T13:08:02Z

Now, ./tcc -run -DTCC_TARGET_X86_64 tcc.c -run tcctest.c works!

Fixes for issues I've just found/introduced to x86 TCC.

2009-04-18T13:08:01Z

- Cast from pointer to long long makes TCC output an error. Use cast to int before we apply shift operation for a pointer value. - Removed test cases for casts from pointer to char/short because they produce warning.

x86-64: Cast from 64bit pointer to long long must not generate movslq.

2009-04-18T13:08:01Z

x86-64: Make ABI for long double compatible with GCC.

2009-04-18T13:08:01Z

- Now we use x87's stack top the long double return values. - Add rc_fret and reg_fret, wrapper functions for RC_FRET and REG_FRET. - Add a test case to check if strto* works OK.

Improve the test coverage: !val for float/double/long long f.

2009-04-18T13:08:01Z

Support long long bitfields for all architectures.

2009-04-18T13:07:09Z

- Modified gv() and vstore(), added vpushll(). - Added a test case for long long bitfields. - Tested on x86 and x86-64.

A uint64 bug fix on x86-64

2009-04-18T13:07:08Z

64bit unsigned literal was handled as 32bit integer. Added a unittest to catch this.

string_test: we should always use 'unsigned int' for b

2009-04-18T13:07:08Z

As recently shown in fb0ac2 (s/int/unsigned/ since GCC 4.3.2 produces code which doesn't stop) comparing (signed) int variable to 0x80000000 is not idea for x86_64. This is not a good idea for x86_32 either, because GCC 4.3.2 (the one in Debian Lenny) rightly assumes that a signed int could be never 0x80000000, and thus removes the check from while (b != 0x80000000) { ... completely. If we want this check, we need b to be always 'unsigned' Signed-off-by: Kirill Smelkov