Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
caisar
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
caisar
Commits
ed2fe1ee
Commit
ed2fe1ee
authored
1 year ago
by
Julien Girard-Satabin
Browse files
Options
Downloads
Patches
Plain Diff
[doc] Clarified ieee 754 floating point requirement in spec
parent
f79bbbbc
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/acas_xu.rst
+5
-1
5 additions, 1 deletion
doc/acas_xu.rst
with
5 additions
and
1 deletion
doc/acas_xu.rst
+
5
−
1
View file @
ed2fe1ee
...
@@ -125,11 +125,15 @@ our theory ``ACASXU_P1``.
...
@@ -125,11 +125,15 @@ our theory ``ACASXU_P1``.
We will need to write down some numerical values. As of now, CAISAR allows
We will need to write down some numerical values. As of now, CAISAR allows
writing values using floating-point arithmetic only. Why3 defines a float type
writing values using floating-point arithmetic only. Why3 defines a float type
and the relevant arithmetic operations according to the IEEE floating-point
and the relevant arithmetic operations according to the IEEE
754
floating-point
standard in a theory, astutely called ``ieee_float``. Specifically, we will
standard in a theory, astutely called ``ieee_float``. Specifically, we will
import the ``Float64`` sub-theory, that defines everything we need for 64-bit
import the ``Float64`` sub-theory, that defines everything we need for 64-bit
precision floating-point numbers. We thus import it in our theory using the
precision floating-point numbers. We thus import it in our theory using the
``use`` keyword.
``use`` keyword.
This currently requires to write exact IEEE 754 floating
point values in the specification file, which is
understandably a setback in terms of usability, but have the
advantage of being unambiguous on the specification.
Our file looks like this so far:
Our file looks like this so far:
...
...
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