-
Notifications
You must be signed in to change notification settings - Fork 769
[SYCL] Allow recursive function calls in a constexpr context. #2105
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
Conversation
It doesn't really make sense to restrict recursion for something that is forced to be evaluated at constexpr time, since this is a restriction due to device limitations. This patch creates a constexpr-context count for all of the constexpr contexts I could create, and creates a counter. It is implemented this way to permit a future implementer to add other diagnostics (such as DLLImport?) as permissible in constexpr.
Ping @premanandrao I think the other two are on vacation today :) Also, I've got no idea on the Jenkins failure, it claims that test_hierarchical_opencl failed, yet there is nothing in this patch that could have caused that. |
I'm working till noon to attend your training today!
I didn't see this fail. The links led me to this failing test - |
LGTM but @premanandrao can you also take a look? |
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.
I thought I had approved it yesterday. :-) |
It doesn't really make sense to restrict recursion for something that is
forced to be evaluated at constexpr time, since this is a restriction
due to device limitations. This patch creates a constexpr-context count
for all of the constexpr contexts I could create, and creates a counter.
It is implemented this way to permit a future implementer to add other
diagnostics (such as DLLImport?) as permissible in constexpr.
This was requested in #2104