You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sycl/doc/extensions/RelaxStdLayout/SYCL_INTEL_relax_standard_layout.asciidoc
+4-3Lines changed: 4 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ Because the interfaces defined by this specification are not final and are subje
48
48
== Version
49
49
50
50
Built On: {docdate} +
51
-
Revision: 1
51
+
Revision: 2
52
52
53
53
== Contact
54
54
Michael Kinsner, Intel (michael 'dot' kinsner 'at' intel 'dot' com)
@@ -59,7 +59,7 @@ This extension is written against the SYCL 1.2.1 specification, Revision 6.
59
59
60
60
== Overview
61
61
62
-
SYCL 1.2.1 required data stored into a buffer or passed as a kernel argument to be standard layout. This is in addition to the data also being trivially copyable. This extension relaxes the standard layout requirement while leaving the trivially copyable requirement intact.
62
+
SYCL 1.2.1 requires data stored into a buffer or passed as a kernel argument to be standard layout. This is in addition to the data also being trivially copyable. This extension relaxes the standard layout requirement while leaving the trivially copyable requirement intact.
63
63
64
64
Standard layout does not guarantee ABI compatibility across devices or between a device and the host, but can help. To avoid introducing incompatible data layouts, this extension also requires device compilers to validate that their layout of data is compatible with that used by the host. There are multiple implementation approaches that can achieve this, although they are beyond the scope of this extension which describes the behavior only.
65
65
@@ -73,7 +73,7 @@ Sharing data structures between host and device code imposes certain restriction
73
73
74
74
==== To:
75
75
76
-
Sharing data structures between host and device code imposes certain restrictions, such as use of only user defined classes that are {cpp}11 trivially copyable classes for the data structures, classes that are {cpp}11 trivially copyable classes for the data structures, and in general, no pointers initialized for the host can be used on the device.
76
+
Sharing data structures between host and device code imposes certain restrictions, such as use of only user defined classes that are {cpp}11 trivially copyable classes for the data structures, and in general, no pointers initialized for the host can be used on the device.
77
77
78
78
=== Modify Sentence in Section 4.8.5 (SYCL function for invoking kernels, +set_arg+ description)
79
79
@@ -148,6 +148,7 @@ None.
148
148
|========================================
149
149
|Rev|Date|Author|Changes
150
150
|1|2020-03-17|Michael Kinsner|*Initial public working draft*
151
+
|2|2020-03-24|Michael Kinsner|Remove repeated sentence and fix typo
0 commit comments