Using this script:
yarpgen --std=c
#../c2m driver.c func.c -ei
gcc -o ygcc driver.c func.c && ./ygcc
tinycc-env tcc -o ytcc driver.c func.c && ./ytcc
It gives different result than gcc after 4 trials:
check-it.sh
/*SEED 2003917550*/
5782830862525388415
1507557374623343254
Sorry !
It was my fault I was testing with a not mob tinycc, using mob the
failed example I've showed before doesn't happen.
Cheers !
On 8/3/23 12:02, Domingo Alvarez Duarte wrote:
Using this script:
yarpgen --std=c
#../c2m driver.c func.c -ei
gcc -o ygcc driver.c func.c && ./ygcc
Thanks Michael.Your commit c771cb52 fixes a lot of bugs in the yarpgen v1 generated tests.For seed values from 1 to 99, only 4 result failures left: 26, 56, 64 and 84.For 100 to 200, there are some more result failures (102, 117 and 173)and some compile aborts: 123, 143, 197.-- bye bye ... Detlef
I added another tcc bug report, discovered by yarpgen (v1).https://savannah.nongnu.org/bugs/?63895Initialization of an array (of struct tf_3_struct_2) is broken.tf_3_struct_2 contains some structs of type tf_3_struct_1and tf_3_struct_1 contains bitfields and non bitfield member,and tcc always
Binaries do not get built - and are omitted from the installation process, in
turn - when running 'make install' before 'make'. Is this a feature, or a bug?
Thanks.
RT___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
