Given the nature of TCC, I prefer to use it when there is a problem with
gcc. It may be able to give me a clue or two as to whether the problem
is caused by patsopt or gcc.
On my old and slow laptop, TCC could handle in less than 2 seconds 500K
(half of a million) lines of C code generated by patsopt. If someone ever
wants
to use ATS to do scripting, using TCC can make a lot of sense.On Tuesday, December 16, 2014 2:55:04 PM UTC-5, Brandon Barker wrote:
Is it being used in Travis CI, or would you even want to?
On Tue, Dec 16, 2014 at 2:52 PM, gmhwxi <gmh...@gmail.com <javascript:>> wrote:
TCC (TCC : Tiny C Compiler) is REALLY fast. When used to bootstrap ATS2,
it is more than 10 times faster than ‘gcc -O2’:
cd ${PATSHOME}/src/CBOOT
time make CC=tcc >& /dev/null
real 0m3.634s
user 0m2.280s
sys 0m0.744s
cd ${PATSHOME}/src/CBOOT
time make CC=gcc >& /dev/null
real 0m41.857s
user 0m34.334s
sys 0m3.900s
I obtained the above numbers on my pretty slow laptop.
I also noted that the compiler (patsopt) generated by TCC
takes about 3X the time needed by the one generated by GCC.
Let’s hope that someone will soon give CompCert a try to see how
it fares when used to bootstrap ATS2 :)On Tuesday, December 16, 2014 2:55:08 PM UTC-5, Raoul Duke wrote:
the wrong answer fast (or slow) might not be so good
