CFGgrind Alternatives

Similar projects and alternatives to CFGgrind

psychec

4 496 7.3 C++ CFGgrind VS psychec

A compiler frontend for the C programming language
jotai-benchmarks

2 31 6.1 C CFGgrind VS jotai-benchmarks

Collection of executable benchmarks
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better CFGgrind alternative or higher similarity.

Suggest an alternative to CFGgrind

CFGgrind reviews and mentions

Posts with mentions or reviews of CFGgrind. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-17.

Tips Performance benchmarks for a custom compiler?
2 projects | /r/Compilers | 17 Jan 2023

But let me suggest Jotai to you. That's a collection with about 30K C programs. They all run without undefined behavior (as per kcc or frama-C). Each program is self-contained. But each program also runs for a very short time. So, I recommend you use CFGGrind to count the number of instructions executed. CFGGrind can separate instructions per function, and each Jotai benchmark consists of a single function. For instance, to count the total number of instructions executed by function foo, you can do (assuming that profile data was saved into a file called `test.cfg`):
The Jotai Benchmark Collection
3 projects | /r/Compilers | 16 Aug 2022

We, at UFMG, have been working on a methodology to generate benchmarks in C. We have a working collection of benchmarks here with a bit more than 30K executable programs. Benchmarks are single functions mined from open-source repositories. We have designed a domain-specific language to generate inputs for them. We use psyche-c to infer missing types and declarations. We use kcc and AddressSanitizier to filter out as much undefined behavior as possible. We use CFGGrind to check input coverage and to count the number of instructions executed. These benchmarks can be used in many ways: to stress test compilers; to autotune predictive compilation tasks; to analyze the dynamic behavior of programs; to improve compiler optimizations; etc. We have a technical report here.