Skip to content

Commit 63ea912

Browse files
committed
fix_typos
1 parent 8335ff5 commit 63ea912

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

sycl/doc/extensions/experimental/sycl_ext_intel_runtime_buffer_location.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ q.parallel_for(sycl::range<1>(N), [=] (sycl::id<1> i){
9191

9292
=== Changes to runtime properties
9393

94-
This extension adds the new property `sycl::ext::intel::experimental::property::usm::buffer_location`` which applications can pass in the property_list parameter to all overloads of the `sycl::malloc_device()`, `sycl::malloc_shared()`, `sycl::malloc_host()` function. However, this property has no effect when passed to `sycl::malloc_shared()`, `sycl::malloc_host()`. Following is a synopsis of this property.
94+
This extension adds the new property `sycl::ext::intel::experimental::property::usm::buffer_location` which applications can pass in the property_list parameter to all overloads of the `sycl::malloc_device()`, `sycl::malloc_shared()`, `sycl::malloc_host()` function. However, this property has no effect when passed to `sycl::malloc_shared()`, `sycl::malloc_host()`. Following is a synopsis of this property.
9595

9696
[source,c++]
9797
----
@@ -106,7 +106,7 @@ class buffer_location {
106106
} // namespace sycl::ext::intel::experimental::property::usm
107107
----
108108

109-
On targets that provide more than one type of global memory, `buffer_location` allows user to specify which of the global memory to allocate memory to. This provide user the flexibility to choose the global memory that satisfy requirements for bandwodth and throughput.
109+
On targets that provide more than one type of global memory, `buffer_location` allows user to specify which of the global memory to allocate memory to. This provide user the flexibility to choose the global memory that satisfy requirements for bandwidth and throughput.
110110

111111
This property is ignored for non-FPGA devices. Attempting to use this extension on other devices or backends will result in no effect.
112112

0 commit comments

Comments
 (0)