Skip to content

[2.7] bpo-36106: resolve sinpi name clash with libm (IEEE-754 violation) (GH-12027)#12050

Merged
serhiy-storchaka merged 2 commits into
python:2.7from
dimpase:py27
Feb 26, 2019
Merged

[2.7] bpo-36106: resolve sinpi name clash with libm (IEEE-754 violation) (GH-12027)#12050
serhiy-storchaka merged 2 commits into
python:2.7from
dimpase:py27

Conversation

@dimpase

@dimpase dimpase commented Feb 26, 2019

Copy link
Copy Markdown
Contributor

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 worked 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)

https://bugs.python.org/issue36106

this is a backport of #12027 to
2.7 branch.

https://bugs.python.org/issue36106

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 worked 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)

https://bugs.python.org/issue36106

this is a backport of python#12027 to
2.7 branch.
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.

4 participants