Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[libc][math] Entry points and tests needed for some already-implemented math functions #84689

Closed
Flandini opened this issue Mar 10, 2024 · 0 comments · Fixed by #88443
Closed
Assignees
Labels

Comments

@Flandini
Copy link
Contributor

From discussion with @lntue, the functions nextafterf128, nexttowardf128, nearbyintf128, and scalbnf128, and nanf128 need entry points and tests added. nanf128 will also need some updates to strtonan to make it work for 128-bit.

I plan to work on these.

@github-actions github-actions bot added the libc label Mar 10, 2024
lntue pushed a commit that referenced this issue Mar 15, 2024
Continuing #84689, this one required more changes than the others, so I
am making it a separate PR.

Extends some stuff in `str_to_float.h`, `str_to_integer.h` to work on
types wider than `unsigned long long` and `uint64_t`.

cc @lntue for review.
lntue pushed a commit that referenced this issue Apr 29, 2024
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant