The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.
From OpenAlex, which stores abstracts as an
index of words and their positions: what is shown is rebuilt from that,
and reads fluently whether or not it is what the author wrote.
Abstract
This paper presents Checked C, an extension to C designed to support spatial safety, implemented in Clang and LLVM. Checked C's design is distinguished by its focus on backward-compatibility, incremental conversion, developer control, and enabling highly performant code. Like past approaches to a safer C, Checked C employs a form of checked pointer whose accesses can be statically or dynamically verified. Performance evaluation on a set of standard benchmark programs shows overheads to be relatively low. More interestingly, Checked C introduces the notions of a checked region and bounds-safe interfaces.
How it got here
How it got here
agent via openalex
Added
2026-10-25 18:53 UTC
Not denied by
a person 2026-10-29 17:12 UTC
Cite it as
@misc{elliott2018checked,
title = {Checked C: Making C Safe by Extension},
author = {Archibald Samuel Elliott and Andrew Ruef and Michael Hicks and David Tarditi},
year = {2018},
journal = {IEEE Cybersecurity Development (SecDev)},
pages = {53--60},
doi = {10.1109/secdev.2018.00015},
}