[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] Fix signedness of LL shift operators in libtcc1.c (gr
Re: [Tinycc-devel] Fix signedness of LL shift operators in libtcc1.c (grischka-2005-09-25 case_10)
Thu, 3 May 2007 17:11:00 -0400
On Thursday 03 May 2007 5:00 pm, David A. Wheeler wrote:
> This bug can only be triggered on certain compilation conditions
> that are NOT true for the normal tcc test harness. In particular, you have
> to be using a version of libtcc1.c that was compiled with __TINYC__ defined.
> On a typical installation this is NOT true. So to force the USE of the
> library code modified here, after you've done ./configure && make
> on tcc, do this when in the tcc build directory:
> ./tcc -c -B. -I. -D__TINYC__ -o x.o libtcc1.c
> mv x.o libtcc1.o
> make libtcc1.a
> rm tcc
> make tcc
> make test
I is confuse-ed.
What's the #define __TINYC__ for? By which I mean why is there a codepath
that doesn't use it, and under what circumstances would it be naturally
enabled (or actually needed) rather than just forced for testing purposes?
(Any time the checkin comment is 5 times the size of the patch, I worry. :)