Skip to content

[SYCL][Doc] Update docs to reflect new compiler features #4030

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.

Sign up for GitHub

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

Merged
pvchupin merged 3 commits into from
Jun 30, 2021
Merged

[SYCL][Doc] Update docs to reflect new compiler features #4030

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
221cda3
[SYCL][Doc] Update docs to reflect new compiler features
Jun 30, 2021
a0f4fc4
Address review comments
Jun 30, 2021
6096745
Limit line length to 80 characters
Jun 30, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 9 additions & 8 deletions sycl/doc/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,14 +38,15 @@ allows one to specify the desired third-party compiler name. Usage example:
`clang++ -fsycl -fsycl-host-compiler=g++ -fsycl-host-compiler-options="-g" test.cpp`

Implicitly, the above command would:
1. turn to the DPC++ compiler for generating the integration header and
compiling the device code for the needed target(s);
2. detect your preferred host compiler (`g++`, in this case) and use it to
compile your host code and the integration header from 1) into a host object file;
3. link the host object file and the device image(s) into the final executable.

To learn more about the compiler options mentioned, and the DPC++ compiler CLI
in general, please refer to the [DPC++ Compiler User Manual](UsersManual.md).
1. turn to the DPC++ compiler for compiling the device code for the needed
target(s) and generating dependencies ("integration files") for the host side;
2. detect your preferred host compiler (`g++`, in this case), then use it to
compile your host code and the dependency files from 1) into host object file(s);
3. link the device image(s) from 1) and the host object(s) from 2) into
the final executable.

To learn more about the compiler options mentioned, and the DPC++ compiler
command-line interface in general, please refer to the [DPC++ Compiler User Manual](UsersManual.md).
To learn more about the concepts behind this flow, and the DPC++ Compiler
internals as such, we welcome you to study our
[DPC++ Compiler and Runtime architecture design](CompilerAndRuntimeDesign.md)
Expand Down