Esteemed tinycc maintainers -

See attached test case.  The #line directive seems to corrupt tinycc's ability to correctly find a .h file in the same directory as the C source file that #includes it.

Expected result of unpacking tinycc_bug.tar.gz; cd tinycc_bug; ./demo

+ gcc -c dir/foo.c
+ gcc -c dir/bad.c
+ tcc -c dir/foo.c
+ tcc -c dir/bad.c

Actual result:

+ gcc -c dir/foo.c
+ gcc -c dir/bad.c
+ tcc -c dir/foo.c
+ tcc -c dir/bad.c
mythical.c:10: error: include file 'simple.h' not found

Note that the only difference between foo.c and bad.c is the presence of the #line directive.

In the production code that "found" this case, the effect was more insidious: by not finding the correct include file, it found a different include file of the same name (through a long list of -I command line options).  The include step therefore succeeded (from tinycc's perspective), but the mistake caused a syntax fault much farther on in the compilation phase.