[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[csmith-dev] csmith running for > 60 minutes (Intel Xeon 4114, Debian-sid/x86-64)



Hello all


Thanks for the csmith tool.



I am surprised that 


csmith --max-block-depth 7 --argc --max-block-size 6 --max-funcs 50


is running for more than one hour of CPU time, using


 csmith --version
csmith 2.4.0
Git version: deddca6

compiled with g++ 11.3 on Debian sid x86/64 (Dell workstation, Intel Xeon4114, 128Gbytes RAM).


BTW, my https://github.com/bstarynk/misc-basile/blob/master/manydl.c program is generating more or less random C files (on Linux only), compiling them, then dlopen(3)-ing them. An experimental difference with csmith is that the generated C code is in practice terminating.  I have no formal proof of that property.


You could also use Jacques Pitrat's CAIA source code (for Linux or MacOSX, downloadable from https://github.com/bstarynk/caia-pitrat and described in his last book: Artificial Beings, the conscience of a conscious machine ISBN .978-1848211018 ..) as a test input for your static C analyzers. All the thousands of C files are self generated by Pitrat's CAIA software.



Regards


Dr Basile Starynkevitch    -   research engineer at CEA, LIST, DILS, LSL
CEA LIST Nano-Innov b862 PC 174 - 91191 GIF/YVETTE CEDEX, France