X-Git-Url: http://git.efficios.com/?p=ctf.git;a=blobdiff_plain;f=common-trace-format-specification.txt;fp=common-trace-format-specification.txt;h=797dec14a53adc3009e11417257323e94635af6b;hp=4ab3ed99861b15af950a26d75722dcec382a2c12;hb=237324a20398c5c8eaf92aff0eace177ef8a747f;hpb=7e58b8bfd86eea7b2929f2ee37dad7e167e11500 diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt index 4ab3ed9..797dec1 100644 --- a/common-trace-format-specification.txt +++ b/common-trace-format-specification.txt @@ -171,20 +171,23 @@ TSDL meta-data attribute representation of a specific alignment: 4.1.3 Byte order -By default, the native endianness of the source architecture is used. -Byte order can be overridden for a basic type by specifying a "byte_order" -attribute. Typical use-case is to specify the network byte order (big endian: -"be") to save data captured from the network into the trace without conversion. -If not specified, the byte order is native. +By default, byte order of a basic type is the byte order described in +the trace description. It can be overridden by specifying a +"byte_order" attribute for a basic type. Typical use-case is to specify +the network byte order (big endian: "be") to save data captured from the +network into the trace without conversion. TSDL meta-data representation: byte_order = native OR network OR be OR le; /* network and be are aliases */ +The "native" keyword selects the byte order described in the trace +description. The "network" byte order is an alias for big endian. + Even though the trace description section is not per se a type, for sake -of clarity, it should be noted that native and network byte orders are -only allowed within type declaration. The byte_order specified in the -trace description section only accepts be OR le values. +of clarity, it should be noted that "native" and "network" byte orders +are only allowed within type declaration. The byte_order specified in +the trace description section only accepts "be" or "le" values. 4.1.4 Size