2002
DOI: 10.1007/3-540-45927-8_15
|View full text |Cite
|
Sign up to set email alerts
|

Asserting the Precision of Floating-Point Computations: A Simple Abstract Interpreter

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
44
0

Year Published

2002
2002
2013
2013

Publication Types

Select...
6
1

Relationship

3
4

Authors

Journals

citations
Cited by 41 publications
(44 citation statements)
references
References 4 publications
0
44
0
Order By: Relevance
“…More recently, static program analysis has provided another way to conduct error analysis [12,6,13,14]. This approach characterizes the error of mathematical operations using a set of static inference rules, allowing a compile-time analysis to determine the worst-case precision of a final result.…”
Section: Related Workmentioning
confidence: 99%
“…More recently, static program analysis has provided another way to conduct error analysis [12,6,13,14]. This approach characterizes the error of mathematical operations using a set of static inference rules, allowing a compile-time analysis to determine the worst-case precision of a final result.…”
Section: Related Workmentioning
confidence: 99%
“…The underlying idea of the concrete model, first sketched in [11], then further described in more details in [18], and meanwhile implemented in a first version of the Fluctuat static analyzer [12], is to describe the difference of behaviour between the execution of a program in real numbers and in floating-point numbers. For that, the concrete value of a program variable is a triplet (f x , r x , e x ), where f x ∈ F is the value of the variable if the program is executed with a finite-precision semantics, r…”
Section: Concrete Modelmentioning
confidence: 99%
“…Another idea of [11,18,12], also developed here, is that it could be of interest for a static analysis to decompose the error term e x along its provenance in the source code of the analyzed program, in order to point out the main sources of numerical discrepancy. For that, depending on the level of detail required, control points, blocks, or functions of a program can be annotated by a label , which will be used to identify the errors introduced during a computation.…”
Section: Concrete Modelmentioning
confidence: 99%
“…We should add that this work started from the difficulty to find good widening and narrowing operators for domains used for characterizing the precision of floating-point computations, used by some of the authors in [15].…”
Section: Introduction and Related Workmentioning
confidence: 99%