BUG: Extend glibc complex trig functions blacklist to glibc < 2.18.#7518
Merged
charris merged 1 commit intonumpy:masterfrom Apr 7, 2016
Merged
BUG: Extend glibc complex trig functions blacklist to glibc < 2.18.#7518charris merged 1 commit intonumpy:masterfrom
charris merged 1 commit intonumpy:masterfrom
Conversation
The library complex trig functions are inaccurate also in glibc versions 2.16 and 2.17, so extend the blacklist. Closes numpy#7517.
Member
|
The problems seem specific to |
Contributor
Author
|
Yes, these problems are specific to |
Member
|
OK, merged. Thanks @nforro . |
This was referenced Apr 7, 2016
Closed
This was referenced Mar 14, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The library complex trig functions are inaccurate also in glibc
versions 2.16 and 2.17, so extend the blacklist.
Closes #7517.