- Mar 25, 2022
-
-
Björn Brandenburg authored
-
Björn Brandenburg authored
-
Björn Brandenburg authored
-
-
- Mar 17, 2022
-
-
This commit renames scope [basic_facts] into [basic_rt_facts] to highlight the that lemmas collected in the scope are real-time (rt) theory lemmas. These new tactics are just shorthand for [(e)auto with basic_rt_facts].
-
- Feb 16, 2022
-
-
There are quite a few places where hypotheses about the task of a job are simply stated as equality (even though a proper predicate exists). This patch replaces the equalities with the predicate.
-
- Jul 26, 2021
-
-
Marco Maida authored
-
- Dec 11, 2020
-
-
The names for job's and task's run-to-completion threshold functions are so long that it often gets in the way of writing theorems and proofs. As a compromise between verbosity and convenience it was decided to rename [task_run_to_completion_threshold] to [task_rtct] and [job_run_to_completion_threshold] to [job_rtct].
-
- Dec 20, 2019
-
-
Sergey Bozhko authored
-
- Dec 19, 2019
-
-
Björn Brandenburg authored
Move everything into the new namespace starting with 'prosa' rather than the bland 'rt'.
-
Björn Brandenburg authored
The main restructuring thrust is nearing completion, so let's get rid of the `restructuring` namespace.
-
Björn Brandenburg authored
improve comments, fix names, move some stuff around
-
- Dec 10, 2019
-
-
Björn Brandenburg authored
This is not yet the final organization, but already an improvement. Move main high-level results to separate top-level `results` module. Rationale: Let's make it very clear where to find the main, high-level results in Prosa, and at the same time let's declutter the analysis namespace. Other notable change, apart from moving files around: - move two key analysis definitions to analysis.definitions - split RBF definition and facts into separate files - move facts about ideal schedule to ideal_schedule.v
-
- Dec 03, 2019
-
-
-
Björn Brandenburg authored
-
Björn Brandenburg authored
-
Björn Brandenburg authored
The two concepts are tightly coupled and it does not make sense to mix and match them. Therefore, it's cleaner and easier to understand if both aspects of the preemption model are instantiated in the same module next to each other.
-
Björn Brandenburg authored
No need to keep the two separate as they are tightly coupled anyway, and the joint file doesn't become too long.
-
Björn Brandenburg authored
-
Björn Brandenburg authored
-
Björn Brandenburg authored
-
Björn Brandenburg authored
-
- Nov 19, 2019
-
-
Björn Brandenburg authored
This fixes all warnings about ambiguous module names and resolves #49. It also highlights that we still need to cut down on superfluous Require Import commands in recently ported files.
-
Sergey Bozhko authored
-