intel / intel/llvm

[Driver] Some SYCL-specific options propagate to FE in non-SYCL mode

Open
#1,493 0 comments 0 reactions 1 assignee Assigned to @mdtoguchi View on GitHub
confirmed enhancement
Dominant language
LLVM
Stars
1.5k
Forks
854
Avg merge
3d 17h
Merged PRs (30d)
137

Description

Generally, when no `fsycl` is given and a SYCL-specific option is passed by the user, we error out (e.g. as is the case with `-fsycl-targets`). `-sycl-std` is a known exception, however:
```bash
clang++ test.cpp -sycl-std=2017 -### 2>&1 | grep sycl-std
```
will show the option's presence in the FE call. It doesn't seem to affect the compilation, therefore is a minor issue by itself.

We should revise the list of SYCL-specific options, making sure that those affecting the compilation require `-fsycl`, and the less critical ones are ignored with a warning.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.