Fix non-determinism in global placement caused by different FFT output values #4518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `fft_test` checks that the FFT output is deterministic despite using floating point values. Signed-off-by: Tim 'mithro' Ansell <tansell@google.com>
GCC per default enables one optimization for x86_64 that can change the result of floating-point operations: -ffp-contract=fast. This allows the compiler to do floating-point expression contraction such as combining multiplication and addition instructions with an FMA instruction. However, the FMA instruction omits the rounding done in the multiplication instruction, making the calculations produce different results for some input values. Disabling floating-point contraction with -ffp-contract=off makes GCC generate code that produces a consistent result for x86_64. See https://kristerw.github.io/2021/11/09/fp-contract/ The `fft_test` checks that this is working correctly. Signed-off-by: Tim 'mithro' Ansell <tansell@google.com>
|
clang-tidy review says "All clean, LGTM! 👍" |
maliberty
approved these changes
Jan 10, 2024
QuantamHD
approved these changes
Jan 10, 2024
mithro
added a commit
to mithro/bazel_rules_hdl
that referenced
this pull request
Jan 10, 2024
This is needed for floating point stability. The global placement depends on the output of the FFT library. Without `-ffp-contract=off` the current FFT library produces different results dependent on if the compiler is targeting an x86 architecture which has the "FMA instruction". The FMA instruction omits the rounding done in the multiplication instruction, making the calculations produce different results for some input values See https://kristerw.github.io/2021/11/09/fp-contract/ See also OpenROAD change @ The-OpenROAD-Project/OpenROAD#4518 Signed-off-by: Tim 'mithro' Ansell <tansell@google.com>
mithro
added a commit
to mithro/bazel_rules_hdl
that referenced
this pull request
Jan 10, 2024
This is needed for floating point stability. The global placement depends on the output of the FFT library. Without `-ffp-contract=off` the current FFT library produces different results dependent on if the compiler is targeting an x86 architecture which has the "FMA instruction". The FMA instruction omits the rounding done in the multiplication instruction, making the calculations produce different results for some input values See https://kristerw.github.io/2021/11/09/fp-contract/ See also OpenROAD change @ The-OpenROAD-Project/OpenROAD#4518 Signed-off-by: Tim Ansell <tansell@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The global placement depends on the output of the FFT library. Without
-ffp-contract=offthe current FFT library produces different results dependent on if the compiler is targeting an x86 architecture which has the "FMA instruction".The FMA instruction omits the rounding done in the multiplication instruction, making the calculations produce different results for some input values
See https://kristerw.github.io/2021/11/09/fp-contract/
This pull request;
-ffp-contract=offon for the whole of OpenROAD to make sure the floating point values are deterministic.