Skip to content

Commit 57092d0

Browse files
Apply comments
1 parent 64640f2 commit 57092d0

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

sycl/doc/LinkedAllocations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ during memory object construction, no allocation takes place at that point.
66
Instead, memory is allocated in each context whenever the SYCL memory object
77
is first accessed there:
88

9-
```C++
9+
```
1010
cl::sycl::buffer<int, 1> buf{cl::sycl::range<1>(1)}; // No allocation here
1111
1212
cl::sycl::queue q;
@@ -27,7 +27,7 @@ that context, but for host allocation commands it might be the case that no
2727
actual memory allocation takes place: either because it is possible to reuse the
2828
data pointer provided by the user:
2929

30-
```C++
30+
```
3131
int val;
3232
cl::sycl::buffer<int, 1> buf{&val, cl::sycl::range<1>(1)};
3333

sycl/doc/index.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,3 +30,4 @@ Developing oneAPI DPC++ Compiler
3030
SpecializationConstants
3131
KernelProgramCache
3232
GlobalObjectsInRuntime
33+
LinkedAllocations

0 commit comments

Comments
 (0)