tinycc/tests/tests2/33_ternary_op.expect

33_ternary_op.c:26: warning: pointer/integer mismatch in conditional expression
0
1
4
9
16
15
18
21
24
27
152
Factor out common type combination as there's overlap between handling types for binary and ternay operations. Factor this into a single routine (combine_types). This uses the structure that gen_op was following, and expr_cond was using as well in the past, which I find easier to reconvene with the standard language. But it reuses the new functions for diagnostics to improve (a little) on what GCC or clang produce :) 2020-01-18 04:36:29 +03:00			`33_ternary_op.c:26: warning: pointer/integer mismatch in conditional expression`
tests: Added numerous tests. 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. 2012-06-18 21:27:32 +04:00			`0`
			`1`
			`4`
			`9`
			`16`
			`15`
			`18`
			`21`
			`24`
			`27`
Factor out common type combination as there's overlap between handling types for binary and ternay operations. Factor this into a single routine (combine_types). This uses the structure that gen_op was following, and expr_cond was using as well in the past, which I find easier to reconvene with the standard language. But it reuses the new functions for diagnostics to improve (a little) on what GCC or clang produce :) 2020-01-18 04:36:29 +03:00			`152`