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

[3.7] bpo-36106: Resolve sinpi name clash with libm (IEEE-754 violation). (GH-12027) #12046

Merged
merged 1 commit into from
Feb 26, 2019

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Feb 26, 2019

The standard math library (libm) may follow IEEE-754 recommendation to
include an implementation of sinPi(), i.e. sinPi(x):=sin(pi*x).
And this triggers a name clash, found by FreeBSD developer
Steve Kargl, who worken on putting sinpi into libm used on FreeBSD
(it has to be named "sinpi", not "sinPi", cf. e.g.
https://en.cppreference.com/w/c/experimental/fpext4).
(cherry picked from commit f57cd82)

Co-authored-by: Dima Pasechnik dimpase@gmail.com

https://bugs.python.org/issue36106

…ythonGH-12027)

The standard math library (libm) may follow IEEE-754 recommendation to
include an implementation of sinPi(), i.e. sinPi(x):=sin(pi*x).
And this triggers a name clash, found by FreeBSD developer
Steve Kargl, who worken on putting sinpi into libm used on FreeBSD
(it has to be named "sinpi", not "sinPi", cf. e.g.
https://en.cppreference.com/w/c/experimental/fpext4).
(cherry picked from commit f57cd82)

Co-authored-by: Dima Pasechnik <dimpase@gmail.com>
@miss-islington
Copy link
Contributor Author

@dimpase and @serhiy-storchaka: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit 4e6646f into python:3.7 Feb 26, 2019
@miss-islington miss-islington deleted the backport-f57cd82-3.7 branch February 26, 2019 07:10
@miss-islington
Copy link
Contributor Author

@dimpase and @serhiy-storchaka: Status check is done, and it's a success ✅ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants