(This is a CC to mailing list) Hello John, Thanks for the suggestion. Here are the executables (both statically linked with musl, they will work under any linux kernel 2.0+): This is my personal website, feel free to download. https://kyryl.tk/pikegcc https://kyryl.tk/piketcc
both compiled with tcc pike.c -g -static -o piketcc gcc pike.c -g -static -o pikegcc gcc 11.20 release tcc (git+git://repo.or.cz/tinycc.git) last commit My software build environment is nothing too out of the ordinary, it's all bleeding edge from the git repos. I don't run some hopelessly outdated system or anything like that. Personally I would find it simple to recreate from source, but anyways, here is a screenshot to better aid in understanding what I am looking at. https://kyryl.tk/2021-11-10-002850_2559x1413_scrot.png What's interesting is even if there is an error and tcc produces bad code, how to does it manage to pass 150+ various test cases non stop for a few hours without faulting once, if as you can see on the screenshot the error gets detected in the simplest of cases imaginable. It seems very likely that valgrind is at fault here. Both gcc and clang compiled versions work with no errors from valgrind on any optimization level. _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
