The tests are taken almost verbatim from the open source project PicoC. It can be found at https://code.google.com/p/picoc/. The tests range from very simple/trivial ones to more complicated. My view is that the more tests the better. Without tests like this I was very reluctant to make any changes to tcc for the fear of breaking things. The tests pass on Win32, OSX, Linux x86 and x86_64. One or two tests fail on each platform due to differences in the runtime library.
		
			
				
	
	
		
			40 lines
		
	
	
	
		
			735 B
		
	
	
	
		
			C
		
	
	
	
	
	
			
		
		
	
	
			40 lines
		
	
	
	
		
			735 B
		
	
	
	
		
			C
		
	
	
	
	
	
| #include <stdio.h>
 | |
| 
 | |
| int main()
 | |
| {
 | |
|    int a;
 | |
|    int b;
 | |
|    int c;
 | |
|    int d;
 | |
|    int e;
 | |
|    int f;
 | |
|    int x;
 | |
|    int y;
 | |
| 
 | |
|    a = 12;
 | |
|    b = 34;
 | |
|    c = 56;
 | |
|    d = 78;
 | |
|    e = 0;
 | |
|    f = 1;
 | |
| 
 | |
|    printf("%d\n", c + d);
 | |
|    printf("%d\n", (y = c + d));
 | |
|    printf("%d\n", e || e && f);
 | |
|    printf("%d\n", e || f && f);
 | |
|    printf("%d\n", e && e || f);
 | |
|    printf("%d\n", e && f || f);
 | |
|    printf("%d\n", a && f | f);
 | |
|    printf("%d\n", a | b ^ c & d);
 | |
|    printf("%d, %d\n", a == a, a == b);
 | |
|    printf("%d, %d\n", a != a, a != b);
 | |
|    printf("%d\n", a != b && c != d);
 | |
|    printf("%d\n", a + b * c / f);
 | |
|    printf("%d\n", a + b * c / f);
 | |
|    printf("%d\n", (4 << 4));
 | |
|    printf("%d\n", (64 >> 4));
 | |
| 
 | |
|    return 0;
 | |
| }
 | |
| 
 | |
| // vim: set expandtab ts=4 sw=3 sts=3 tw=80 :
 |