svenvh wrote:
> When someone passes the `-Xclang -cl-ext=+all`, the compiler should add
> defines for all the supported extensions.
Indeed; we already have such a list in `opencl-c-base.h` to enable all
header-only extensions for the `spir`/`spirv` targets, so it should be easy to
make `-cl-e
vmustya wrote:
> That way, header-only extensions don't need to be added to
> `OpenCLExtensions.def`
@svenvh, in any case, we need a list of all the supported extensions, including
the header ones. When someone passes the `-Xclang -cl-ext=+all`, the compiler
should add defines for all the sup
svenvh wrote:
> @svenvh, I'm trying to unify the extensions enablement in the user interface.
> We can enable or disable some of the extensions with the `-Xclang
> -cl-ext=+extension` command line options. For example, a user can pass
> `-Xclang -cl-ext=+cl_khr_subgroups` successfully, but the
vmustya wrote:
> What is the motivation for this change? We are trying to move away from
> adding extensions to this file for extensions that only add builtin
> functions, see e.g. https://reviews.llvm.org/D92231 . What functionality are
> you gaining by adding them here?
@svenvh, I'm trying
https://github.com/svenvh requested changes to this pull request.
What is the motivation for this change? We are trying to move away from adding
extensions to this file for extensions that only add builtin functions, see
e.g. https://reviews.llvm.org/D92231 . What functionality are you gainin
https://github.com/michalpaszkowski approved this pull request.
https://github.com/llvm/llvm-project/pull/129777
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
