aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen
diff options
context:
space:
mode:
authorjeanPerier <jperier@nvidia.com>2025-01-30 14:24:45 +0100
committerGitHub <noreply@github.com>2025-01-30 14:24:45 +0100
commit2e581dc54b8983122528ade578824d70ec42b503 (patch)
tree4f9c90987347b9b0b9206d556968b04cd2aacb75 /clang/lib/CodeGen
parent104c2b86a5e9f4871707b25399735f0e5db58745 (diff)
downloadllvm-2e581dc54b8983122528ade578824d70ec42b503.zip
llvm-2e581dc54b8983122528ade578824d70ec42b503.tar.gz
llvm-2e581dc54b8983122528ade578824d70ec42b503.tar.bz2
[flang][NFC] make IR generation for ieee_next deterministic (#125055)
C++ function call argument evaluation order is unspecified. When piping functions that generates IR, this creates indeterminism in the IR generated by flang (e.g., depend which C++ compiler compiled flang). While it has interesting fuzzing property for flang (Initially, most of expression lowering used that pattern for binary operation where Fortran also does not specify any order, and we did found bugs exposed by some of the IR version and not the other), it is not ideal for lit tests (I found this because of a CI failure when not properly adding `-DAG` [in test updates](https://github.com/llvm/llvm-project/pull/124966)), and many people also really value bit to bit reproducibility from compilers.
Diffstat (limited to 'clang/lib/CodeGen')
0 files changed, 0 insertions, 0 deletions