-
Notifications
You must be signed in to change notification settings - Fork 45
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
Element Restriction Oriented #889
Conversation
Co-authored-by: Jeremy L Thompson <jeremy@jeremylt.org>
Co-authored-by: Jeremy L Thompson <jeremy@jeremylt.org>
1635b39
to
c774505
Compare
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.
LGTM. If CI is happy, I'm happy
:), thanks for your comments. @jedbrown do you have any comments? |
Yeah, I was hoping changing the function signature to static inline int CeedElemRestrictionApply_Ref_Core(CeedElemRestriction r,
const CeedInt num_comp, const CeedInt blk_size, const CeedInt comp_stride,
CeedInt start, CeedInt stop, CeedTransposeMode t_mode, const bool is_oriented,
CeedVector u, CeedVector v, CeedRequest *request) but not creating a bunch of separate variants would be enough for all of the compilers we use to fairly reliably generate good code. |
Why CI is failing? |
CI on LV is flakey |
Added
CeedElemRestrictionCreateOriented
to flip dofs (multiply by -1) if needed for H(div) implementation.