As for OpenCL C, we will allow printf and other variadic functions (prefixed by "__") in C++ mode.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
cfe/trunk/test/SemaOpenCL/extensions.cl | ||
---|---|---|
31 | Shoudn't we move this test to test/SemaOpenCLCXX? |
cfe/trunk/test/SemaOpenCL/extensions.cl | ||
---|---|---|
31 |
Right now test/SemaOpenCLCXX and other corresponding folders contain only functionality specific to C++. In test/SemaOpenCL we will keep tests that are OpenCL C compatible even though we are parsing some of them in C++ mode too. We could create a common folder but I don't see much value in this. Let me know if you have other thoughts.
Yes, I perfectly agree. I would like to make sure that the header is parsed successfully in C++ mode. So it is not just for printf. There are a few other places where we parse the header, I can move this into them if you prefer. May be test/Driver/include-default-header.cl would make more sense to show the intent? |
May be test/Driver/include-default-header.cl would make more sense to show the intent?
test/Headers/opencl-c-header.cl sounds like good candidate.
Shoudn't we move this test to test/SemaOpenCLCXX?
Does -finclude-default-header include opencl-c.h? I think it's an overkill to test that OpenCL C++ allows printf. Ideally we should minimize number of times we parsing 11500+ lines header in LIT tests.