2019 IEEE/ACM 3rd International Workshop on Software Correctness for HPC Applications (Correctness) 2019
DOI: 10.1109/correctness49594.2019.00009
|View full text |Cite
|
Sign up to set email alerts
|

Tool Integration for Source-Level Mixed Precision

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
4
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 16 publications
(6 citation statements)
references
References 21 publications
0
4
0
Order By: Relevance
“…In that, our approach is related to mixed-precision tuning techniques that mostly focus on implementations that mix single, double and quad floating-point precision. Some of these use dynamic analysis to estimate errors and thus do not provide sound guarantees [25,19,17,15], and others use static analysis with accuracy guarantees, but less scalability [5,9]. Mixed-precision tuning generally works well when the target error bounds are close to the error bounds of uniform-precision implementations [9,27].…”
Section: Related Workmentioning
confidence: 99%
“…In that, our approach is related to mixed-precision tuning techniques that mostly focus on implementations that mix single, double and quad floating-point precision. Some of these use dynamic analysis to estimate errors and thus do not provide sound guarantees [25,19,17,15], and others use static analysis with accuracy guarantees, but less scalability [5,9]. Mixed-precision tuning generally works well when the target error bounds are close to the error bounds of uniform-precision implementations [9,27].…”
Section: Related Workmentioning
confidence: 99%
“…Complications typically arise due to (i) the different treatment of built-ins compared to user-defined types by the C++ language causing compilation errors [19], and (ii) the usage of external libraries [18], [20] and C-language function calls [21] that are not compatible with the AD type (as seen in LULESH). While tools exist to (partially) automate the process of the type change [22], these may not be able to handle, e.g., external solver libraries, which require special treatment in the adjoint context [23].…”
Section: A Ad-enhancement Of Luleshmentioning
confidence: 99%
“…In [3] a benchmark suite of programs is introduced for mixed precision computing analysis. Moreover the authors present the performance of various precision auto-tuning algorithms such as combinational (used in FloatSmith [4]), compositional (used in FloatSmith [4]), Delta Debug (introduced in [5], used in Precimonious [6] and PROMISE [1]), hierarchical (used in CRAFT-HPC [7]), hierarchical-compositional (used in FloatSmith [4]) and a Genetic Search Algorithm (GA) (used in AMPT-GA [8]). The Delta Debug algorithm requires multiple executions of the user program to provide a suitable type configuration.…”
Section: Introductionmentioning
confidence: 99%