2021 Forum on Specification &Amp; Design Languages (FDL) 2021
DOI: 10.1109/fdl53530.2021.9568373
|View full text |Cite
|
Sign up to set email alerts
|

Synchronised Shared Memory and Model Checking: A Proof of Concept

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2024
2024
2024
2024

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 7 publications
0
1
0
Order By: Relevance
“…However, this includes schedules that may require runtimedependent changes in the ordering of methods, for example, if a policy does not return to its initial state in each tick. Such policies are not supported by the current static compilation approach in SCCharts and either require a policy-conformant scheduling at runtime or an exploration of the program's state space at compile time, e. g., as illustrated by Aguado and Duenas [AD21] utilizing model checking. Hence, SPs in SCCharts only support a subset of policy automata at this point, specifically those that can be statically transformed into SDs. SDs are a special case of stateless SP automata that always return to their initial state after a tick and specify precedences which methods can be uniquely assigned to scheduling groups (indices) and classified as conflicting (listing themselfs in their blocking set) or commuting.…”
Section: Scheduling Policiesmentioning
confidence: 99%
“…However, this includes schedules that may require runtimedependent changes in the ordering of methods, for example, if a policy does not return to its initial state in each tick. Such policies are not supported by the current static compilation approach in SCCharts and either require a policy-conformant scheduling at runtime or an exploration of the program's state space at compile time, e. g., as illustrated by Aguado and Duenas [AD21] utilizing model checking. Hence, SPs in SCCharts only support a subset of policy automata at this point, specifically those that can be statically transformed into SDs. SDs are a special case of stateless SP automata that always return to their initial state after a tick and specify precedences which methods can be uniquely assigned to scheduling groups (indices) and classified as conflicting (listing themselfs in their blocking set) or commuting.…”
Section: Scheduling Policiesmentioning
confidence: 99%