-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
don't inline float64^float64 #42966
Merged
oscardssmith
merged 13 commits into
JuliaLang:master
from
oscardssmith:remove-float64float64-inline
Nov 10, 2021
Merged
don't inline float64^float64 #42966
Changes from 12 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
07ded3c
don't inline float64^float64
oscardssmith 10c4a6b
fix literal_pow to be more accurate for large negative bases
oscardssmith bcf5e27
fixup! fix literal_pow to be more accurate for large negative bases
oscardssmith 9a3c9db
fix matrix^int
oscardssmith 0e7e160
restrict special case to small ints
oscardssmith e34a79d
fix broken
oscardssmith e3704bb
fix part 2
oscardssmith 1ef574f
Update base/intfuncs.jl
oscardssmith be196d7
why is this so annoying
oscardssmith ac3677f
remove the last inlines.
KristofferC ce5b5f3
fix another bug
oscardssmith 0d5a68c
inv(x)!=x
oscardssmith 04cd0fb
document reason for literal_pow change
oscardssmith File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add some comment on this? Is this to improve performance, accuracy, or both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea. The reasoning is that computing
inv(x)^(-p)
rounds twice. Once to computeinv(x)
and once to compute the power. Since theFloat64^Float64
code works to half an ULP (even for negative numbers), we want to let that code handle the negative powers since it does so better.