-
Notifications
You must be signed in to change notification settings - Fork 49
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
QFunction multi source support #841
Conversation
This one change should be ready to merge. Future changes related to the design of GPU backends can be captured in the refactor discussed in #839. |
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.
I'm fine with this as a step to go ahead and add the desired new feature (multi-file QFunction support) while limiting the scope of the PR. At first I wasn't sure how I felt about elevating the LoadSourceToBuffer
to the interface level since it's only used for GPU backends, but we already do that in, e.g., CeedVectorSyncArray
, which is only really needed for GPU backends, as well, so I think it's fine.
1967cb5
to
30601ac
Compare
Co-authored-by: Jed Brown <[email protected]>
Co-authored-by: Jed Brown <[email protected]>
f5c7dae
to
b44031f
Compare
design to return null pointer when property not present consistent with rest of interface
This PR adds support for multiple QFunction source files.
See the new
t406-qfunction
for usage.I think further downstream consequences of the new
CeedLoadSourceToBuffer()
should be put in a downstream PR.This the bulk of what was in #826, but with some of the possible downstream changes removed. The minor changes to the debugging macros went into #840.