miniblog.

← Back to all posts
Jul 13, 2018 at 19:05
Profiling symbolic execution by measuring the symbolic heap and the symbolic execution graph to ensure solver-aided tools are performant: https://2018.splashcon.org/event/splash-2018-oopsla-finding-code-that-explodes-under-symbolic-evaluation (Part of the remarkable Rosette project.)
Finding Code That Explodes Under Symbolic Evaluation (SPLASH 2018 - OOPSLA) - SPLASH 2018
PACMPL (OOPSLA) seeks contributions on all aspects of programming languages and software engineering. Authors of papers published in PACMPL will present their work at OOPSLA in Boston. Papers may target any stage of software development, including requirements, modeling, prototyping, design, implementation, generation, analysis, verification, testing, evaluation, maintenance, and reuse of software systems. Contributions may include the development of new tools (such as language front-ends, program analyses, and runtime systems), new techniques (such as methodologies, design processes, and ...

Related Posts

Dec 25, 2022 at 03:18
I don't care what your project's test coverage is, but the fact that you're measuring it is a great sign.
Dec 20, 2022 at 05:20
On the challenge of measuring spam prevalence externally, because historical data tends to be cleaner:
Cyber Policy Center | FSI
Feb 5, 2022 at 06:22
Measuring Go program (GoAWK) performance from 1.2 to 1.18: https://benhoyt.com/writings/go-version-performance/ The Go 1.3 runtime led to a 2x speedup in GoAWK, and performance wins have continued since. It's easy to see popular PLs as largely finished, but the wins here show there's still opportunities.
Go performance from version 1.2 to 1.18
Shows how much the performance of Go has improved from version 1.2 through to 1.18 -- in its compiler, runtime, and libraries.