CFGgrind
A dynamic control flow graph (CFG) reconstruction plugin for valgrind. (by rimsa)
jotai-benchmarks
Collection of executable benchmarks (by lac-dcc)
CFGgrind | jotai-benchmarks | |
---|---|---|
2 | 2 | |
102 | 31 | |
- | - | |
4.6 | 6.1 | |
4 months ago | 5 months ago | |
C | C | |
- | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CFGgrind
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?
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
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.
jotai-benchmarks
Posts with mentions or reviews of jotai-benchmarks.
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?
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
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.
What are some alternatives?
When comparing CFGgrind and jotai-benchmarks you can also consider the following projects:
psychec - A compiler frontend for the C programming language
termux-ndk - android-ndk for termux
dstep - A tool for converting C and Objective-C headers to D modules
checkedc - Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe. The goal is to let people easily make their existing C code type-safe and eliminate entire classes of errors. Checked C does not address use-after-free errors. This repo has a wiki for Checked C, sample code, the specification, and test code.
llvmbox - Self contained, fully static llvm tools & libs
CSpydr - A static typed low-level compiled programming language inspired by Rust and C
linux - Linux kernel source tree