-
Notifications
You must be signed in to change notification settings - Fork 36
Support for multiple FFT backends via backend tokens/types #146
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
Open
nHackel
wants to merge
6
commits into
JuliaMath:master
Choose a base branch
from
nHackel:nh/backend
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+98
−24
Open
Changes from 3 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
9fef024
Add backend-based interface
nHackel be75369
Adapt TestPlans module to backend approach.
nHackel 23f04cf
Try fixing "user-facing"/default plan for real/complex integer|ration…
nHackel 6e90f12
Try implementing backend via scopedvalues
nHackel 4b86b65
Fix method amib. in convert(BackendRef)
nHackel a25ba9e
Improve return type infer.
nHackel 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 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
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
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
Oops, something went wrong.
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.
A major caveat is that this is thread-unsafe. Maybe a task-local storage or a scope value would be better options? They may come at a performance penalty though, not sure. Alternatively, not having a global state would be better.
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 point! I also tried playing around a bit with ScopedValues. I just didn't see a way where I could preserve the "default" behaviour of
plan_fft
with it, since the user would always need to do:I did see ScopedSettings.jl, which would allow for the desired behaviour but I'm not sure if such an additional non-base dependency is justified.
Another option would be to have both a "global" active backend and a dynamic backend with the later being a ScopedValue. Then the "high-level" API would need to first check if the dynamic scoped value is set, if not then check the global one and if neither is set throw the no-backend-error.
I'm not sure if packages that want to actively switch between backends, should target the high-level interface. The current behaviour if multiple FFT backends are loaded is also not well-defined at the moment