Re: [Tinycc-devel] more comments

[fabrice . bellard]

Quoting Greg Haerr <address@hidden>:

> Fabrice,
>     I've finished with some more testing using tcc, and have found the
> following, after using tcc to compile Microwindows:
> 
> 1. I finally found the bug that crashes the tcc compiler.  The
> following program will cause an internal segfault:
> 
> f()
> {
>     extern int *a;
>     *a = 1;
> }
> g()
> {
>     extern int *a;
>     *a = 1;
> }

It will be fixed in next release.

> 2. Programs in MSDOS/Windows CRLF text format
> won't compile.  (preprocessor chokes on CR, it seems)

Arg. I'll fix the parser to handle '\r' as space. Maybe it would be interesting
to be slightly different from the ANSI standard to accept \n or \r\n as line
feed (for '\' at end of line for example).

> 3. Programs using original K&R function declaration
> format won't compile. "a(b) int b; {}"
> I'm changing all mwin programs to ANSI format.

It will be fixed in next release.

> 4.  __FUNCTION__ and __LINE__ aren't defined.

It will be fixed in next release.

> 5. tcc issues a "-- expected" errmsg when the last arg in a
> tcc command is a -L/usr/lib/...  I'm still working on this one,
> it's a little strange.  I've gotten around this bug by removing
> the makefile options that put the extra arg there.

Currently all options come before the .c or .o files. Since you are not the
first to ask it, I'll fix it.

> 6. When tcc is used as a linker and passed several .o and
> then some .a files,  it appears that the .a symbols aren't searched
> twice for symbols that are required.  (works with gcc).  I'm not
> sure if there's a topological sort occuring before using the .a
> symbols.
> I'm still looking into this one.

Can you explain more ?

Fabrice.