[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [csmith-dev] Tiny project idea
Thank you very much. That shall be useful. I can try to fuse it with someones shoosh reversin results. Was it also made by reversers? Ill check license and toy with idea of replacing dwarf with pdb where it may make sense.
On Thu, Apr 15, 2021 at 6:01 PM pawel k. <email@example.com> wrote:
> Thank You for ultra quick reply and valuable hint.
> Hmm maybe i shall use those. I like the featurette yours are more realistic possibly why i am prejudiced ones you mention may produce random garbage that doesnt exist in wilderness but i for sure will try other approach if you suggest so. I very much respect your opinion your work and publications and everything.
> We also could use likewise of csmith for hdls like verilog and friends if not for other langs. See vloghammer project for example.
> Btw pls send greetings to checkedc guys in msrd as well as vs team. I like their works.
> If we could learn the internals of pdb format for foss i would be super duper happy.
You can find some documentation (& pointers to other documentation) on
the PDB format here: https://llvm.org/docs/PDB/index.html
> Best regards,
> Pawel Kunio
> pt., 16.04.2021, 02:44 użytkownik Xuejun Yang <firstname.lastname@example.org> napisał:
>> Csmith spends most of its time doing generation-time analysis and uses the results to avoid generating undefined code. Because of the analysis, the generation speed is quite slow compared to other "less intelligent" fuzzers. Currently there is no easy way to disable that behavior.
>> Have you searched the field and found no other C program generator that is faster than Csmith but doesn't care about undefined behaviors?
>> On Thu, Apr 15, 2021 at 1:26 PM pawel k. <email@example.com> wrote:
>>> I love your project and publications and findings.
>>> Im pondering a little side project based on csmith. I would like to test bin codesize between diff compilers. In this version, avoiding undef behaviours would be less relevant.
>>> Id run the testsuites and genned code from your tool hrough my harness measuring func sizes. Im thinking initially of two versions:
>>> One would measure sizes of all functions, one only of available ones. Thus first version would interfere a bit with inliner and dce while other would respect them.
>>> Im initially thinking of measuring clang vs gcc possibly on common set of targets available on both compilers.
>>> Please let me know if that makes sense.
>>> Looking forward to it.
>>> Best regards,
>>> Pawel Kunio