-
Notifications
You must be signed in to change notification settings - Fork 795
[SYCL] Add support for [[intel::reqd_sub_group_… #2137
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
Changes from all commits
1554ae7
a655790
65b3634
f3cdca1
9eb186f
804f147
8d2c340
07aa988
59dde52
7c4204e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
// RUN: %clang_cc1 -fsycl -fsycl-is-device -fsyntax-only -ast-dump -verify -pedantic %s | FileCheck %s | ||
|
||
// Test that checkes template parameter support for 'intel_reqd_sub_group_size' attribute on sycl device. | ||
// Test that checkes template parameter support for 'reqd_sub_group_size' attribute on sycl device. | ||
|
||
template <int SIZE> | ||
class KernelFunctor { | ||
public: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It feels weird to me that existing tests all throw warnings now. I am not sure what is usually done when spellings are changed though. Personally I would just prefer updating these tests to use the new spelling (except where this functionality is actually being checked). @erichkeane thoughts? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I could go either way. There aren't that many tests to just 'fix' the spelling of here, so I'd probably suggest just fixing all the spellings instead. If this was more widespread (that is, the tests were a pain to change), or a situation where there was a difference in the implementation, I'd consider just using the -Wno flag in the tests. In this case, I think just changing the spelling in the tests is better than adding the warning/note to ALL of them. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That said, probably leave at least 1 to validate the deprecated warning :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yea. That's what I meant by 'except where this functionality is actually being checked' :) @smanna12 sorry but can you make this change? I think it's just cleaner this way. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Sure. I will do this. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you still need to leave ONE example (perhaps add a new example) to validate the new warning/note. Done There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, right. By mistake, I changed all spellings. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry for the multiple submission. |
||
//expected-error@+1{{'intel_reqd_sub_group_size' attribute requires a positive integral compile time constant expression}} | ||
[[cl::intel_reqd_sub_group_size(SIZE)]] void operator()() {} | ||
// expected-error@+1{{'reqd_sub_group_size' attribute requires a positive integral compile time constant expression}} | ||
[[intel::reqd_sub_group_size(SIZE)]] void operator()() {} | ||
}; | ||
|
||
int main() { | ||
|
Uh oh!
There was an error while loading. Please reload this page.