diff options
| author | Michael Flanders <flanders.michaelk@gmail.com> | 2024-04-29 18:25:45 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-29 19:25:45 -0400 |
| commit | 5e9937d1b3ada9c686505c5f2c1e1b054ad9edc2 (patch) | |
| tree | 1fa5edf7513221c8a6a45df956e8cc45c36c0d0c /llvm/lib/CodeGen/MachineFunctionAnalysis.cpp | |
| parent | c4c4e17c99f8d4f79bb9e1e3819d1d76e5e09ed1 (diff) | |
| download | llvm-5e9937d1b3ada9c686505c5f2c1e1b054ad9edc2.zip llvm-5e9937d1b3ada9c686505c5f2c1e1b054ad9edc2.tar.gz llvm-5e9937d1b3ada9c686505c5f2c1e1b054ad9edc2.tar.bz2 | |
[libc][math] Adds entrypoint and tests for nearbyintf128,scalbnf128 (#88443)
Closes #84689.
Adding @lntue for review.
I was curious about the implementation of
`round_using_current_rounding_mode` used for the `nearbyint` functions.
It has one of the rounding modes as unreachable
([here](https://github.com/llvm/llvm-project/blob/main/libc/src/__support/FPUtil/NearestIntegerOperations.h#L243)),
and I was wondering if this was okay for the `nearbyint` functions.
---------
Co-authored-by: Michael Flanders <mkf727@cs.washington.edu>
Diffstat (limited to 'llvm/lib/CodeGen/MachineFunctionAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions