Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
W
WSymb
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
OTAWA-plugins
WSymb
Commits
4bea62a2
Commit
4bea62a2
authored
5 years ago
by
Forget Julien
Browse files
Options
Downloads
Patches
Plain Diff
Added doc on how to use procedures that have a parametric WCET.
parent
b28f090f
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+15
-1
15 additions, 1 deletion
README.md
with
15 additions
and
1 deletion
README.md
+
15
−
1
View file @
4bea62a2
...
@@ -21,7 +21,7 @@ Please remove "nospam" from the email addresses.
...
@@ -21,7 +21,7 @@ Please remove "nospam" from the email addresses.
WSymb is a WCET analysis tool. Its main specificity is that, instead of
WSymb is a WCET analysis tool. Its main specificity is that, instead of
a constant WCET, it computes a
*WCET formula*
, where symbols (or
a constant WCET, it computes a
*WCET formula*
, where symbols (or
parameters) can correspond to various kind of values unnkown at analysis
parameters) can correspond to various kind
s
of values unnkown at analysis
time. The formula can later be
*instanciated*
, when parameter values are
time. The formula can later be
*instanciated*
, when parameter values are
known. For more details on the underlying theory, check out the papers
known. For more details on the underlying theory, check out the papers
[1,2].
[1,2].
...
@@ -145,6 +145,20 @@ identifiers to their values. In this example, the WCET is successively
...
@@ -145,6 +145,20 @@ identifiers to their values. In this example, the WCET is successively
instantiated with values ranges from 0 to 20 for parameter 1. Parameter
instantiated with values ranges from 0 to 20 for parameter 1. Parameter
identifiers are visible in the
`.pwf`
file.
identifiers are visible in the
`.pwf`
file.
### Procedures with a parametric WCET
You can specify a procedure for which the WCET is a parameter (i.e. the
WCET of the procedure is considered to be unknown by
`dumpcft`
). To do
so:
1.
Write a
`.pfl`
file, where each line consists of a procedure name and
a parameter identifier (an integer);
2.
Pass that file as an argument to
`dumpcft`
. This produces a
`.pwf`
file, where the WCET of the procedure is replaced by the
corresponding parameter idenfitier;
3.
For parameter instanciation, see the example
`pwcet_instantiator.c`
,
where the procedure
`param_valuation`
relates parameter identifiers
to their values (same as for parametric loop bounds).
----
----
## References
## References
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment