Proceedings of the 42nd ACM SIGPLAN International Conference on Programming Language Design and Implementation 2021
DOI: 10.1145/3453483.3454081
|View full text |Cite
|
Sign up to set email alerts
|

Automatically enforcing fresh and consistent inputs in intermittent systems

Abstract: Intermittently powered energy-harvesting devices enable new applications in inaccessible environments. Program executions must be robust to unpredictable power failures, introducing new challenges in programmability and correctness. One hard problem is that input operations have implicit constraints, embedded in the behavior of continuously powered executions, on when input values can be collected and used. This paper aims to develop a formal framework for enforcing these constraints. We identify two key prope… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
3
3
1

Relationship

1
6

Authors

Journals

citations
Cited by 15 publications
(7 citation statements)
references
References 65 publications
0
7
0
Order By: Relevance
“…For the design of MEMIC, we set the following design objectives, derived from the background section and relevant literature [2], [3], [12], [29], [30]:…”
Section: A Objectivesmentioning
confidence: 99%
“…For the design of MEMIC, we set the following design objectives, derived from the background section and relevant literature [2], [3], [12], [29], [30]:…”
Section: A Objectivesmentioning
confidence: 99%
“…Safeguards for Learning. There has been some exploration of the safety challenges involved in online ML [23,24,33,37]. For example, the authors of [24] discuss a fallback policy when the model performs badly.…”
Section: Related Workmentioning
confidence: 99%
“…Although prior works have suggested correctness models for intermittent execution based on data dependencies, they bypass the discussion on persist dependencies by assuming an architecture with no bu ering of dirty data (e.g. a write-through cache) [41,42]. We consider an architecture where all load and store instructions access NVM addresses, with a volatile write-back cache acting as an intermediary.…”
Section: Intermittent Persist Dependenciesmentioning
confidence: 99%