| 1 | Common Trace Format (CTF) Specification (v1.8.1) |
| 2 | |
| 3 | Mathieu Desnoyers, EfficiOS Inc. |
| 4 | |
| 5 | The goal of the present document is to specify a trace format that suits the |
| 6 | needs of the embedded, telecom, high-performance and kernel communities. It is |
| 7 | based on the Common Trace Format Requirements (v1.4) document. It is designed to |
| 8 | allow traces to be natively generated by the Linux kernel, Linux user-space |
| 9 | applications written in C/C++, and hardware components. One major element of |
| 10 | CTF is the Trace Stream Description Language (TSDL) which flexibility |
| 11 | enables description of various binary trace stream layouts. |
| 12 | |
| 13 | The latest version of this document can be found at: |
| 14 | |
| 15 | git tree: git://git.efficios.com/ctf.git |
| 16 | gitweb: http://git.efficios.com/?p=ctf.git |
| 17 | |
| 18 | A reference implementation of a library to read and write this trace format is |
| 19 | being implemented within the BabelTrace project, a converter between trace |
| 20 | formats. The development tree is available at: |
| 21 | |
| 22 | git tree: git://git.efficios.com/babeltrace.git |
| 23 | gitweb: http://git.efficios.com/?p=babeltrace.git |
| 24 | |
| 25 | The CE Workgroup of the Linux Foundation, Ericsson, and EfficiOS have |
| 26 | sponsored this work. |
| 27 | |
| 28 | |
| 29 | Table of Contents |
| 30 | |
| 31 | 1. Preliminary definitions |
| 32 | 2. High-level representation of a trace |
| 33 | 3. Event stream |
| 34 | 4. Types |
| 35 | 4.1 Basic types |
| 36 | 4.1.1 Type inheritance |
| 37 | 4.1.2 Alignment |
| 38 | 4.1.3 Byte order |
| 39 | 4.1.4 Size |
| 40 | 4.1.5 Integers |
| 41 | 4.1.6 GNU/C bitfields |
| 42 | 4.1.7 Floating point |
| 43 | 4.1.8 Enumerations |
| 44 | 4.2 Compound types |
| 45 | 4.2.1 Structures |
| 46 | 4.2.2 Variants (Discriminated/Tagged Unions) |
| 47 | 4.2.3 Arrays |
| 48 | 4.2.4 Sequences |
| 49 | 4.2.5 Strings |
| 50 | 5. Event Packet Header |
| 51 | 5.1 Event Packet Header Description |
| 52 | 5.2 Event Packet Context Description |
| 53 | 6. Event Structure |
| 54 | 6.1 Event Header |
| 55 | 6.1.1 Type 1 - Few event IDs |
| 56 | 6.1.2 Type 2 - Many event IDs |
| 57 | 6.2 Event Context |
| 58 | 6.3 Event Payload |
| 59 | 6.3.1 Padding |
| 60 | 6.3.2 Alignment |
| 61 | 7. Trace Stream Description Language (TSDL) |
| 62 | 7.1 Meta-data |
| 63 | 7.2 Declaration vs Definition |
| 64 | 7.3 TSDL Scopes |
| 65 | 7.3.1 Lexical Scope |
| 66 | 7.3.2 Static and Dynamic Scopes |
| 67 | 7.4 TSDL Examples |
| 68 | 8. Clocks |
| 69 | |
| 70 | |
| 71 | 1. Preliminary definitions |
| 72 | |
| 73 | - Event Trace: An ordered sequence of events. |
| 74 | - Event Stream: An ordered sequence of events, containing a subset of the |
| 75 | trace event types. |
| 76 | - Event Packet: A sequence of physically contiguous events within an event |
| 77 | stream. |
| 78 | - Event: This is the basic entry in a trace. (aka: a trace record). |
| 79 | - An event identifier (ID) relates to the class (a type) of event within |
| 80 | an event stream. |
| 81 | e.g. event: irq_entry. |
| 82 | - An event (or event record) relates to a specific instance of an event |
| 83 | class. |
| 84 | e.g. event: irq_entry, at time X, on CPU Y |
| 85 | - Source Architecture: Architecture writing the trace. |
| 86 | - Reader Architecture: Architecture reading the trace. |
| 87 | |
| 88 | |
| 89 | 2. High-level representation of a trace |
| 90 | |
| 91 | A trace is divided into multiple event streams. Each event stream contains a |
| 92 | subset of the trace event types. |
| 93 | |
| 94 | The final output of the trace, after its generation and optional transport over |
| 95 | the network, is expected to be either on permanent or temporary storage in a |
| 96 | virtual file system. Because each event stream is appended to while a trace is |
| 97 | being recorded, each is associated with a distinct set of files for |
| 98 | output. Therefore, a stored trace can be represented as a directory |
| 99 | containing zero, one or more files per stream. |
| 100 | |
| 101 | Meta-data description associated with the trace contains information on |
| 102 | trace event types expressed in the Trace Stream Description Language |
| 103 | (TSDL). This language describes: |
| 104 | |
| 105 | - Trace version. |
| 106 | - Types available. |
| 107 | - Per-trace event header description. |
| 108 | - Per-stream event header description. |
| 109 | - Per-stream event context description. |
| 110 | - Per-event |
| 111 | - Event type to stream mapping. |
| 112 | - Event type to name mapping. |
| 113 | - Event type to ID mapping. |
| 114 | - Event context description. |
| 115 | - Event fields description. |
| 116 | |
| 117 | |
| 118 | 3. Event stream |
| 119 | |
| 120 | An event stream can be divided into contiguous event packets of variable |
| 121 | size. An event packet can contain a certain amount of padding at the |
| 122 | end. The stream header is repeated at the beginning of each event |
| 123 | packet. The rationale for the event stream design choices is explained |
| 124 | in Appendix B. Stream Header Rationale. |
| 125 | |
| 126 | The event stream header will therefore be referred to as the "event packet |
| 127 | header" throughout the rest of this document. |
| 128 | |
| 129 | |
| 130 | 4. Types |
| 131 | |
| 132 | Types are organized as type classes. Each type class belong to either of two |
| 133 | kind of types: basic types or compound types. |
| 134 | |
| 135 | 4.1 Basic types |
| 136 | |
| 137 | A basic type is a scalar type, as described in this section. It includes |
| 138 | integers, GNU/C bitfields, enumerations, and floating point values. |
| 139 | |
| 140 | 4.1.1 Type inheritance |
| 141 | |
| 142 | Type specifications can be inherited to allow deriving types from a |
| 143 | type class. For example, see the uint32_t named type derived from the "integer" |
| 144 | type class below ("Integers" section). Types have a precise binary |
| 145 | representation in the trace. A type class has methods to read and write these |
| 146 | types, but must be derived into a type to be usable in an event field. |
| 147 | |
| 148 | 4.1.2 Alignment |
| 149 | |
| 150 | We define "byte-packed" types as aligned on the byte size, namely 8-bit. |
| 151 | We define "bit-packed" types as following on the next bit, as defined by the |
| 152 | "Integers" section. |
| 153 | |
| 154 | Each basic type must specify its alignment, in bits. Examples of |
| 155 | possible alignments are: bit-packed (align = 1), byte-packed (align = |
| 156 | 8), or word-aligned (e.g. align = 32 or align = 64). The choice depends |
| 157 | on the architecture preference and compactness vs performance trade-offs |
| 158 | of the implementation. Architectures providing fast unaligned write |
| 159 | byte-packed basic types to save space, aligning each type on byte |
| 160 | boundaries (8-bit). Architectures with slow unaligned writes align types |
| 161 | on specific alignment values. If no specific alignment is declared for a |
| 162 | type, it is assumed to be bit-packed for integers with size not multiple |
| 163 | of 8 bits and for gcc bitfields. All other basic types are byte-packed |
| 164 | by default. It is however recommended to always specify the alignment |
| 165 | explicitly. Alignment values must be power of two. Compound types are |
| 166 | aligned as specified in their individual specification. |
| 167 | |
| 168 | TSDL meta-data attribute representation of a specific alignment: |
| 169 | |
| 170 | align = value; /* value in bits */ |
| 171 | |
| 172 | 4.1.3 Byte order |
| 173 | |
| 174 | By default, the native endianness of the source architecture is used. |
| 175 | Byte order can be overridden for a basic type by specifying a "byte_order" |
| 176 | attribute. Typical use-case is to specify the network byte order (big endian: |
| 177 | "be") to save data captured from the network into the trace without conversion. |
| 178 | If not specified, the byte order is native. |
| 179 | |
| 180 | TSDL meta-data representation: |
| 181 | |
| 182 | byte_order = native OR network OR be OR le; /* network and be are aliases */ |
| 183 | |
| 184 | 4.1.4 Size |
| 185 | |
| 186 | Type size, in bits, for integers and floats is that returned by "sizeof()" in C |
| 187 | multiplied by CHAR_BIT. |
| 188 | We require the size of "char" and "unsigned char" types (CHAR_BIT) to be fixed |
| 189 | to 8 bits for cross-endianness compatibility. |
| 190 | |
| 191 | TSDL meta-data representation: |
| 192 | |
| 193 | size = value; (value is in bits) |
| 194 | |
| 195 | 4.1.5 Integers |
| 196 | |
| 197 | Signed integers are represented in two-complement. Integer alignment, |
| 198 | size, signedness and byte ordering are defined in the TSDL meta-data. |
| 199 | Integers aligned on byte size (8-bit) and with length multiple of byte |
| 200 | size (8-bit) correspond to the C99 standard integers. In addition, |
| 201 | integers with alignment and/or size that are _not_ a multiple of the |
| 202 | byte size are permitted; these correspond to the C99 standard bitfields, |
| 203 | with the added specification that the CTF integer bitfields have a fixed |
| 204 | binary representation. A MIT-licensed reference implementation of the |
| 205 | CTF portable bitfields is available at: |
| 206 | |
| 207 | http://git.efficios.com/?p=babeltrace.git;a=blob;f=include/babeltrace/bitfield.h |
| 208 | |
| 209 | Binary representation of integers: |
| 210 | |
| 211 | - On little and big endian: |
| 212 | - Within a byte, high bits correspond to an integer high bits, and low bits |
| 213 | correspond to low bits. |
| 214 | - On little endian: |
| 215 | - Integer across multiple bytes are placed from the less significant to the |
| 216 | most significant. |
| 217 | - Consecutive integers are placed from lower bits to higher bits (even within |
| 218 | a byte). |
| 219 | - On big endian: |
| 220 | - Integer across multiple bytes are placed from the most significant to the |
| 221 | less significant. |
| 222 | - Consecutive integers are placed from higher bits to lower bits (even within |
| 223 | a byte). |
| 224 | |
| 225 | This binary representation is derived from the bitfield implementation in GCC |
| 226 | for little and big endian. However, contrary to what GCC does, integers can |
| 227 | cross units boundaries (no padding is required). Padding can be explicitly |
| 228 | added (see 4.1.6 GNU/C bitfields) to follow the GCC layout if needed. |
| 229 | |
| 230 | TSDL meta-data representation: |
| 231 | |
| 232 | integer { |
| 233 | signed = true OR false; /* default false */ |
| 234 | byte_order = native OR network OR be OR le; /* default native */ |
| 235 | size = value; /* value in bits, no default */ |
| 236 | align = value; /* value in bits */ |
| 237 | /* based used for pretty-printing output, default: decimal. */ |
| 238 | base = decimal OR dec OR OR d OR i OR u OR 10 OR hexadecimal OR hex OR x OR X OR p OR 16 |
| 239 | OR octal OR oct OR o OR 8 OR binary OR b OR 2; |
| 240 | /* character encoding, default: none */ |
| 241 | encoding = none or UTF8 or ASCII; |
| 242 | } |
| 243 | |
| 244 | Example of type inheritance (creation of a uint32_t named type): |
| 245 | |
| 246 | typealias integer { |
| 247 | size = 32; |
| 248 | signed = false; |
| 249 | align = 32; |
| 250 | } := uint32_t; |
| 251 | |
| 252 | Definition of a named 5-bit signed bitfield: |
| 253 | |
| 254 | typealias integer { |
| 255 | size = 5; |
| 256 | signed = true; |
| 257 | align = 1; |
| 258 | } := int5_t; |
| 259 | |
| 260 | The character encoding field can be used to specify that the integer |
| 261 | must be printed as a text character when read. e.g.: |
| 262 | |
| 263 | typealias integer { |
| 264 | size = 8; |
| 265 | align = 8; |
| 266 | signed = false; |
| 267 | encoding = UTF8; |
| 268 | } := utf_char; |
| 269 | |
| 270 | |
| 271 | 4.1.6 GNU/C bitfields |
| 272 | |
| 273 | The GNU/C bitfields follow closely the integer representation, with a |
| 274 | particularity on alignment: if a bitfield cannot fit in the current unit, the |
| 275 | unit is padded and the bitfield starts at the following unit. The unit size is |
| 276 | defined by the size of the type "unit_type". |
| 277 | |
| 278 | TSDL meta-data representation: |
| 279 | |
| 280 | unit_type name:size; |
| 281 | |
| 282 | As an example, the following structure declared in C compiled by GCC: |
| 283 | |
| 284 | struct example { |
| 285 | short a:12; |
| 286 | short b:5; |
| 287 | }; |
| 288 | |
| 289 | The example structure is aligned on the largest element (short). The second |
| 290 | bitfield would be aligned on the next unit boundary, because it would not fit in |
| 291 | the current unit. |
| 292 | |
| 293 | 4.1.7 Floating point |
| 294 | |
| 295 | The floating point values byte ordering is defined in the TSDL meta-data. |
| 296 | |
| 297 | Floating point values follow the IEEE 754-2008 standard interchange formats. |
| 298 | Description of the floating point values include the exponent and mantissa size |
| 299 | in bits. Some requirements are imposed on the floating point values: |
| 300 | |
| 301 | - FLT_RADIX must be 2. |
| 302 | - mant_dig is the number of digits represented in the mantissa. It is specified |
| 303 | by the ISO C99 standard, section 5.2.4, as FLT_MANT_DIG, DBL_MANT_DIG and |
| 304 | LDBL_MANT_DIG as defined by <float.h>. |
| 305 | - exp_dig is the number of digits represented in the exponent. Given that |
| 306 | mant_dig is one bit more than its actual size in bits (leading 1 is not |
| 307 | needed) and also given that the sign bit always takes one bit, exp_dig can be |
| 308 | specified as: |
| 309 | |
| 310 | - sizeof(float) * CHAR_BIT - FLT_MANT_DIG |
| 311 | - sizeof(double) * CHAR_BIT - DBL_MANT_DIG |
| 312 | - sizeof(long double) * CHAR_BIT - LDBL_MANT_DIG |
| 313 | |
| 314 | TSDL meta-data representation: |
| 315 | |
| 316 | floating_point { |
| 317 | exp_dig = value; |
| 318 | mant_dig = value; |
| 319 | byte_order = native OR network OR be OR le; |
| 320 | align = value; |
| 321 | } |
| 322 | |
| 323 | Example of type inheritance: |
| 324 | |
| 325 | typealias floating_point { |
| 326 | exp_dig = 8; /* sizeof(float) * CHAR_BIT - FLT_MANT_DIG */ |
| 327 | mant_dig = 24; /* FLT_MANT_DIG */ |
| 328 | byte_order = native; |
| 329 | align = 32; |
| 330 | } := float; |
| 331 | |
| 332 | TODO: define NaN, +inf, -inf behavior. |
| 333 | |
| 334 | Bit-packed, byte-packed or larger alignments can be used for floating |
| 335 | point values, similarly to integers. |
| 336 | |
| 337 | 4.1.8 Enumerations |
| 338 | |
| 339 | Enumerations are a mapping between an integer type and a table of strings. The |
| 340 | numerical representation of the enumeration follows the integer type specified |
| 341 | by the meta-data. The enumeration mapping table is detailed in the enumeration |
| 342 | description within the meta-data. The mapping table maps inclusive value |
| 343 | ranges (or single values) to strings. Instead of being limited to simple |
| 344 | "value -> string" mappings, these enumerations map |
| 345 | "[ start_value ... end_value ] -> string", which map inclusive ranges of |
| 346 | values to strings. An enumeration from the C language can be represented in |
| 347 | this format by having the same start_value and end_value for each element, which |
| 348 | is in fact a range of size 1. This single-value range is supported without |
| 349 | repeating the start and end values with the value = string declaration. |
| 350 | |
| 351 | enum name : integer_type { |
| 352 | somestring = start_value1 ... end_value1, |
| 353 | "other string" = start_value2 ... end_value2, |
| 354 | yet_another_string, /* will be assigned to end_value2 + 1 */ |
| 355 | "some other string" = value, |
| 356 | ... |
| 357 | }; |
| 358 | |
| 359 | If the values are omitted, the enumeration starts at 0 and increment of 1 for |
| 360 | each entry. An entry with omitted value that follows a range entry takes |
| 361 | as value the end_value of the previous range + 1: |
| 362 | |
| 363 | enum name : unsigned int { |
| 364 | ZERO, |
| 365 | ONE, |
| 366 | TWO, |
| 367 | TEN = 10, |
| 368 | ELEVEN, |
| 369 | }; |
| 370 | |
| 371 | Overlapping ranges within a single enumeration are implementation defined. |
| 372 | |
| 373 | A nameless enumeration can be declared as a field type or as part of a typedef: |
| 374 | |
| 375 | enum : integer_type { |
| 376 | ... |
| 377 | } |
| 378 | |
| 379 | Enumerations omitting the container type ": integer_type" use the "int" |
| 380 | type (for compatibility with C99). The "int" type must be previously |
| 381 | declared. E.g.: |
| 382 | |
| 383 | typealias integer { size = 32; align = 32; signed = true } := int; |
| 384 | |
| 385 | enum { |
| 386 | ... |
| 387 | } |
| 388 | |
| 389 | |
| 390 | 4.2 Compound types |
| 391 | |
| 392 | Compound are aggregation of type declarations. Compound types include |
| 393 | structures, variant, arrays, sequences, and strings. |
| 394 | |
| 395 | 4.2.1 Structures |
| 396 | |
| 397 | Structures are aligned on the largest alignment required by basic types |
| 398 | contained within the structure. (This follows the ISO/C standard for structures) |
| 399 | |
| 400 | TSDL meta-data representation of a named structure: |
| 401 | |
| 402 | struct name { |
| 403 | field_type field_name; |
| 404 | field_type field_name; |
| 405 | ... |
| 406 | }; |
| 407 | |
| 408 | Example: |
| 409 | |
| 410 | struct example { |
| 411 | integer { /* Nameless type */ |
| 412 | size = 16; |
| 413 | signed = true; |
| 414 | align = 16; |
| 415 | } first_field_name; |
| 416 | uint64_t second_field_name; /* Named type declared in the meta-data */ |
| 417 | }; |
| 418 | |
| 419 | The fields are placed in a sequence next to each other. They each |
| 420 | possess a field name, which is a unique identifier within the structure. |
| 421 | The identifier is not allowed to use any reserved keyword |
| 422 | (see Section C.1.2). Replacing reserved keywords with |
| 423 | underscore-prefixed field names is recommended. Fields starting with an |
| 424 | underscore should have their leading underscore removed by the CTF trace |
| 425 | readers. |
| 426 | |
| 427 | A nameless structure can be declared as a field type or as part of a typedef: |
| 428 | |
| 429 | struct { |
| 430 | ... |
| 431 | } |
| 432 | |
| 433 | Alignment for a structure compound type can be forced to a minimum value |
| 434 | by adding an "align" specifier after the declaration of a structure |
| 435 | body. This attribute is read as: align(value). The value is specified in |
| 436 | bits. The structure will be aligned on the maximum value between this |
| 437 | attribute and the alignment required by the basic types contained within |
| 438 | the structure. e.g. |
| 439 | |
| 440 | struct { |
| 441 | ... |
| 442 | } align(32) |
| 443 | |
| 444 | 4.2.2 Variants (Discriminated/Tagged Unions) |
| 445 | |
| 446 | A CTF variant is a selection between different types. A CTF variant must |
| 447 | always be defined within the scope of a structure or within fields |
| 448 | contained within a structure (defined recursively). A "tag" enumeration |
| 449 | field must appear in either the same static scope, prior to the variant |
| 450 | field (in field declaration order), in an upper static scope , or in an |
| 451 | upper dynamic scope (see Section 7.3.2). The type selection is indicated |
| 452 | by the mapping from the enumeration value to the string used as variant |
| 453 | type selector. The field to use as tag is specified by the "tag_field", |
| 454 | specified between "< >" after the "variant" keyword for unnamed |
| 455 | variants, and after "variant name" for named variants. |
| 456 | |
| 457 | The alignment of the variant is the alignment of the type as selected by the tag |
| 458 | value for the specific instance of the variant. The alignment of the type |
| 459 | containing the variant is independent of the variant alignment. The size of the |
| 460 | variant is the size as selected by the tag value for the specific instance of |
| 461 | the variant. |
| 462 | |
| 463 | Each variant type selector possess a field name, which is a unique |
| 464 | identifier within the variant. The identifier is not allowed to use any |
| 465 | reserved keyword (see Section C.1.2). Replacing reserved keywords with |
| 466 | underscore-prefixed field names is recommended. Fields starting with an |
| 467 | underscore should have their leading underscore removed by the CTF trace |
| 468 | readers. |
| 469 | |
| 470 | |
| 471 | A named variant declaration followed by its definition within a structure |
| 472 | declaration: |
| 473 | |
| 474 | variant name { |
| 475 | field_type sel1; |
| 476 | field_type sel2; |
| 477 | field_type sel3; |
| 478 | ... |
| 479 | }; |
| 480 | |
| 481 | struct { |
| 482 | enum : integer_type { sel1, sel2, sel3, ... } tag_field; |
| 483 | ... |
| 484 | variant name <tag_field> v; |
| 485 | } |
| 486 | |
| 487 | An unnamed variant definition within a structure is expressed by the following |
| 488 | TSDL meta-data: |
| 489 | |
| 490 | struct { |
| 491 | enum : integer_type { sel1, sel2, sel3, ... } tag_field; |
| 492 | ... |
| 493 | variant <tag_field> { |
| 494 | field_type sel1; |
| 495 | field_type sel2; |
| 496 | field_type sel3; |
| 497 | ... |
| 498 | } v; |
| 499 | } |
| 500 | |
| 501 | Example of a named variant within a sequence that refers to a single tag field: |
| 502 | |
| 503 | variant example { |
| 504 | uint32_t a; |
| 505 | uint64_t b; |
| 506 | short c; |
| 507 | }; |
| 508 | |
| 509 | struct { |
| 510 | enum : uint2_t { a, b, c } choice; |
| 511 | unsigned int seqlen; |
| 512 | variant example <choice> v[seqlen]; |
| 513 | } |
| 514 | |
| 515 | Example of an unnamed variant: |
| 516 | |
| 517 | struct { |
| 518 | enum : uint2_t { a, b, c, d } choice; |
| 519 | /* Unrelated fields can be added between the variant and its tag */ |
| 520 | int32_t somevalue; |
| 521 | variant <choice> { |
| 522 | uint32_t a; |
| 523 | uint64_t b; |
| 524 | short c; |
| 525 | struct { |
| 526 | unsigned int field1; |
| 527 | uint64_t field2; |
| 528 | } d; |
| 529 | } s; |
| 530 | } |
| 531 | |
| 532 | Example of an unnamed variant within an array: |
| 533 | |
| 534 | struct { |
| 535 | enum : uint2_t { a, b, c } choice; |
| 536 | variant <choice> { |
| 537 | uint32_t a; |
| 538 | uint64_t b; |
| 539 | short c; |
| 540 | } v[10]; |
| 541 | } |
| 542 | |
| 543 | Example of a variant type definition within a structure, where the defined type |
| 544 | is then declared within an array of structures. This variant refers to a tag |
| 545 | located in an upper static scope. This example clearly shows that a variant |
| 546 | type definition referring to the tag "x" uses the closest preceding field from |
| 547 | the static scope of the type definition. |
| 548 | |
| 549 | struct { |
| 550 | enum : uint2_t { a, b, c, d } x; |
| 551 | |
| 552 | typedef variant <x> { /* |
| 553 | * "x" refers to the preceding "x" enumeration in the |
| 554 | * static scope of the type definition. |
| 555 | */ |
| 556 | uint32_t a; |
| 557 | uint64_t b; |
| 558 | short c; |
| 559 | } example_variant; |
| 560 | |
| 561 | struct { |
| 562 | enum : int { x, y, z } x; /* This enumeration is not used by "v". */ |
| 563 | example_variant v; /* |
| 564 | * "v" uses the "enum : uint2_t { a, b, c, d }" |
| 565 | * tag. |
| 566 | */ |
| 567 | } a[10]; |
| 568 | } |
| 569 | |
| 570 | 4.2.3 Arrays |
| 571 | |
| 572 | Arrays are fixed-length. Their length is declared in the type |
| 573 | declaration within the meta-data. They contain an array of "inner type" |
| 574 | elements, which can refer to any type not containing the type of the |
| 575 | array being declared (no circular dependency). The length is the number |
| 576 | of elements in an array. |
| 577 | |
| 578 | TSDL meta-data representation of a named array: |
| 579 | |
| 580 | typedef elem_type name[length]; |
| 581 | |
| 582 | A nameless array can be declared as a field type within a structure, e.g.: |
| 583 | |
| 584 | uint8_t field_name[10]; |
| 585 | |
| 586 | Arrays are always aligned on their element alignment requirement. |
| 587 | |
| 588 | 4.2.4 Sequences |
| 589 | |
| 590 | Sequences are dynamically-sized arrays. They refer to a a "length" |
| 591 | unsigned integer field, which must appear in either the same static scope, |
| 592 | prior to the sequence field (in field declaration order), in an upper |
| 593 | static scope, or in an upper dynamic scope (see Section 7.3.2). This |
| 594 | length field represents the number of elements in the sequence. The |
| 595 | sequence per se is an array of "inner type" elements. |
| 596 | |
| 597 | TSDL meta-data representation for a sequence type definition: |
| 598 | |
| 599 | struct { |
| 600 | unsigned int length_field; |
| 601 | typedef elem_type typename[length_field]; |
| 602 | typename seq_field_name; |
| 603 | } |
| 604 | |
| 605 | A sequence can also be declared as a field type, e.g.: |
| 606 | |
| 607 | struct { |
| 608 | unsigned int length_field; |
| 609 | long seq_field_name[length_field]; |
| 610 | } |
| 611 | |
| 612 | Multiple sequences can refer to the same length field, and these length |
| 613 | fields can be in a different upper dynamic scope: |
| 614 | |
| 615 | e.g., assuming the stream.event.header defines: |
| 616 | |
| 617 | stream { |
| 618 | ... |
| 619 | id = 1; |
| 620 | event.header := struct { |
| 621 | uint16_t seq_len; |
| 622 | }; |
| 623 | }; |
| 624 | |
| 625 | event { |
| 626 | ... |
| 627 | stream_id = 1; |
| 628 | fields := struct { |
| 629 | long seq_a[stream.event.header.seq_len]; |
| 630 | char seq_b[stream.event.header.seq_len]; |
| 631 | }; |
| 632 | }; |
| 633 | |
| 634 | The sequence elements follow the "array" specifications. |
| 635 | |
| 636 | 4.2.5 Strings |
| 637 | |
| 638 | Strings are an array of bytes of variable size and are terminated by a '\0' |
| 639 | "NULL" character. Their encoding is described in the TSDL meta-data. In |
| 640 | absence of encoding attribute information, the default encoding is |
| 641 | UTF-8. |
| 642 | |
| 643 | TSDL meta-data representation of a named string type: |
| 644 | |
| 645 | typealias string { |
| 646 | encoding = UTF8 OR ASCII; |
| 647 | } := name; |
| 648 | |
| 649 | A nameless string type can be declared as a field type: |
| 650 | |
| 651 | string field_name; /* Use default UTF8 encoding */ |
| 652 | |
| 653 | Strings are always aligned on byte size. |
| 654 | |
| 655 | 5. Event Packet Header |
| 656 | |
| 657 | The event packet header consists of two parts: the "event packet header" |
| 658 | is the same for all streams of a trace. The second part, the "event |
| 659 | packet context", is described on a per-stream basis. Both are described |
| 660 | in the TSDL meta-data. The packets are aligned on architecture-page-sized |
| 661 | addresses. |
| 662 | |
| 663 | Event packet header (all fields are optional, specified by TSDL meta-data): |
| 664 | |
| 665 | - Magic number (CTF magic number: 0xC1FC1FC1) specifies that this is a |
| 666 | CTF packet. This magic number is optional, but when present, it should |
| 667 | come at the very beginning of the packet. |
| 668 | - Trace UUID, used to ensure the event packet match the meta-data used. |
| 669 | (note: we cannot use a meta-data checksum in every cases instead of a |
| 670 | UUID because meta-data can be appended to while tracing is active) |
| 671 | This field is optional. |
| 672 | - Stream ID, used as reference to stream description in meta-data. |
| 673 | This field is optional if there is only one stream description in the |
| 674 | meta-data, but becomes required if there are more than one stream in |
| 675 | the TSDL meta-data description. |
| 676 | |
| 677 | Event packet context (all fields are optional, specified by TSDL meta-data): |
| 678 | |
| 679 | - Event packet content size (in bits). |
| 680 | - Event packet size (in bits, includes padding). |
| 681 | - Event packet content checksum. Checksum excludes the event packet |
| 682 | header. |
| 683 | - Per-stream event packet sequence count (to deal with UDP packet loss). The |
| 684 | number of significant sequence counter bits should also be present, so |
| 685 | wrap-arounds are dealt with correctly. |
| 686 | - Time-stamp at the beginning and time-stamp at the end of the event packet. |
| 687 | Both timestamps are written in the packet header, but sampled respectively |
| 688 | while (or before) writing the first event and while (or after) writing the |
| 689 | last event in the packet. The inclusive range between these timestamps should |
| 690 | include all event timestamps assigned to events contained within the packet. |
| 691 | - Events discarded count |
| 692 | - Snapshot of a per-stream free-running counter, counting the number of |
| 693 | events discarded that were supposed to be written in the stream after |
| 694 | the last event in the event packet. |
| 695 | * Note: producer-consumer buffer full condition can fill the current |
| 696 | event packet with padding so we know exactly where events have been |
| 697 | discarded. However, if the buffer full condition chooses not |
| 698 | to fill the current event packet with padding, all we know |
| 699 | about the timestamp range in which the events have been |
| 700 | discarded is that it is somewhere between the beginning and |
| 701 | the end of the packet. |
| 702 | - Lossless compression scheme used for the event packet content. Applied |
| 703 | directly to raw data. New types of compression can be added in following |
| 704 | versions of the format. |
| 705 | 0: no compression scheme |
| 706 | 1: bzip2 |
| 707 | 2: gzip |
| 708 | 3: xz |
| 709 | - Cypher used for the event packet content. Applied after compression. |
| 710 | 0: no encryption |
| 711 | 1: AES |
| 712 | - Checksum scheme used for the event packet content. Applied after encryption. |
| 713 | 0: no checksum |
| 714 | 1: md5 |
| 715 | 2: sha1 |
| 716 | 3: crc32 |
| 717 | |
| 718 | 5.1 Event Packet Header Description |
| 719 | |
| 720 | The event packet header layout is indicated by the trace packet.header |
| 721 | field. Here is a recommended structure type for the packet header with |
| 722 | the fields typically expected (although these fields are each optional): |
| 723 | |
| 724 | struct event_packet_header { |
| 725 | uint32_t magic; |
| 726 | uint8_t uuid[16]; |
| 727 | uint32_t stream_id; |
| 728 | }; |
| 729 | |
| 730 | trace { |
| 731 | ... |
| 732 | packet.header := struct event_packet_header; |
| 733 | }; |
| 734 | |
| 735 | If the magic number is not present, tools such as "file" will have no |
| 736 | mean to discover the file type. |
| 737 | |
| 738 | If the uuid is not present, no validation that the meta-data actually |
| 739 | corresponds to the stream is performed. |
| 740 | |
| 741 | If the stream_id packet header field is missing, the trace can only |
| 742 | contain a single stream. Its "id" field can be left out, and its events |
| 743 | don't need to declare a "stream_id" field. |
| 744 | |
| 745 | |
| 746 | 5.2 Event Packet Context Description |
| 747 | |
| 748 | Event packet context example. These are declared within the stream declaration |
| 749 | in the meta-data. All these fields are optional. If the packet size field is |
| 750 | missing, the whole stream only contains a single packet. If the content |
| 751 | size field is missing, the packet is filled (no padding). The content |
| 752 | and packet sizes include all headers. |
| 753 | |
| 754 | An example event packet context type: |
| 755 | |
| 756 | struct event_packet_context { |
| 757 | uint64_t timestamp_begin; |
| 758 | uint64_t timestamp_end; |
| 759 | uint32_t checksum; |
| 760 | uint32_t stream_packet_count; |
| 761 | uint32_t events_discarded; |
| 762 | uint32_t cpu_id; |
| 763 | uint32_t/uint16_t content_size; |
| 764 | uint32_t/uint16_t packet_size; |
| 765 | uint8_t compression_scheme; |
| 766 | uint8_t encryption_scheme; |
| 767 | uint8_t checksum_scheme; |
| 768 | }; |
| 769 | |
| 770 | |
| 771 | 6. Event Structure |
| 772 | |
| 773 | The overall structure of an event is: |
| 774 | |
| 775 | 1 - Stream Packet Context (as specified by the stream meta-data) |
| 776 | 2 - Event Header (as specified by the stream meta-data) |
| 777 | 3 - Stream Event Context (as specified by the stream meta-data) |
| 778 | 4 - Event Context (as specified by the event meta-data) |
| 779 | 5 - Event Payload (as specified by the event meta-data) |
| 780 | |
| 781 | This structure defines an implicit dynamic scoping, where variants |
| 782 | located in inner structures (those with a higher number in the listing |
| 783 | above) can refer to the fields of outer structures (with lower number in |
| 784 | the listing above). See Section 7.3 TSDL Scopes for more detail. |
| 785 | |
| 786 | 6.1 Event Header |
| 787 | |
| 788 | Event headers can be described within the meta-data. We hereby propose, as an |
| 789 | example, two types of events headers. Type 1 accommodates streams with less than |
| 790 | 31 event IDs. Type 2 accommodates streams with 31 or more event IDs. |
| 791 | |
| 792 | One major factor can vary between streams: the number of event IDs assigned to |
| 793 | a stream. Luckily, this information tends to stay relatively constant (modulo |
| 794 | event registration while trace is being recorded), so we can specify different |
| 795 | representations for streams containing few event IDs and streams containing |
| 796 | many event IDs, so we end up representing the event ID and time-stamp as |
| 797 | densely as possible in each case. |
| 798 | |
| 799 | The header is extended in the rare occasions where the information cannot be |
| 800 | represented in the ranges available in the standard event header. They are also |
| 801 | used in the rare occasions where the data required for a field could not be |
| 802 | collected: the flag corresponding to the missing field within the missing_fields |
| 803 | array is then set to 1. |
| 804 | |
| 805 | Types uintX_t represent an X-bit unsigned integer, as declared with |
| 806 | either: |
| 807 | |
| 808 | typealias integer { size = X; align = X; signed = false } := uintX_t; |
| 809 | |
| 810 | or |
| 811 | |
| 812 | typealias integer { size = X; align = 1; signed = false } := uintX_t; |
| 813 | |
| 814 | 6.1.1 Type 1 - Few event IDs |
| 815 | |
| 816 | - Aligned on 32-bit (or 8-bit if byte-packed, depending on the architecture |
| 817 | preference). |
| 818 | - Native architecture byte ordering. |
| 819 | - For "compact" selection |
| 820 | - Fixed size: 32 bits. |
| 821 | - For "extended" selection |
| 822 | - Size depends on the architecture and variant alignment. |
| 823 | |
| 824 | struct event_header_1 { |
| 825 | /* |
| 826 | * id: range: 0 - 30. |
| 827 | * id 31 is reserved to indicate an extended header. |
| 828 | */ |
| 829 | enum : uint5_t { compact = 0 ... 30, extended = 31 } id; |
| 830 | variant <id> { |
| 831 | struct { |
| 832 | uint27_t timestamp; |
| 833 | } compact; |
| 834 | struct { |
| 835 | uint32_t id; /* 32-bit event IDs */ |
| 836 | uint64_t timestamp; /* 64-bit timestamps */ |
| 837 | } extended; |
| 838 | } v; |
| 839 | } align(32); /* or align(8) */ |
| 840 | |
| 841 | |
| 842 | 6.1.2 Type 2 - Many event IDs |
| 843 | |
| 844 | - Aligned on 16-bit (or 8-bit if byte-packed, depending on the architecture |
| 845 | preference). |
| 846 | - Native architecture byte ordering. |
| 847 | - For "compact" selection |
| 848 | - Size depends on the architecture and variant alignment. |
| 849 | - For "extended" selection |
| 850 | - Size depends on the architecture and variant alignment. |
| 851 | |
| 852 | struct event_header_2 { |
| 853 | /* |
| 854 | * id: range: 0 - 65534. |
| 855 | * id 65535 is reserved to indicate an extended header. |
| 856 | */ |
| 857 | enum : uint16_t { compact = 0 ... 65534, extended = 65535 } id; |
| 858 | variant <id> { |
| 859 | struct { |
| 860 | uint32_t timestamp; |
| 861 | } compact; |
| 862 | struct { |
| 863 | uint32_t id; /* 32-bit event IDs */ |
| 864 | uint64_t timestamp; /* 64-bit timestamps */ |
| 865 | } extended; |
| 866 | } v; |
| 867 | } align(16); /* or align(8) */ |
| 868 | |
| 869 | |
| 870 | 6.2 Event Context |
| 871 | |
| 872 | The event context contains information relative to the current event. |
| 873 | The choice and meaning of this information is specified by the TSDL |
| 874 | stream and event meta-data descriptions. The stream context is applied |
| 875 | to all events within the stream. The stream context structure follows |
| 876 | the event header. The event context is applied to specific events. Its |
| 877 | structure follows the stream context structure. |
| 878 | |
| 879 | An example of stream-level event context is to save the event payload size with |
| 880 | each event, or to save the current PID with each event. These are declared |
| 881 | within the stream declaration within the meta-data: |
| 882 | |
| 883 | stream { |
| 884 | ... |
| 885 | event.context := struct { |
| 886 | uint pid; |
| 887 | uint16_t payload_size; |
| 888 | }; |
| 889 | }; |
| 890 | |
| 891 | An example of event-specific event context is to declare a bitmap of missing |
| 892 | fields, only appended after the stream event context if the extended event |
| 893 | header is selected. NR_FIELDS is the number of fields within the event (a |
| 894 | numeric value). |
| 895 | |
| 896 | event { |
| 897 | context = struct { |
| 898 | variant <id> { |
| 899 | struct { } compact; |
| 900 | struct { |
| 901 | uint1_t missing_fields[NR_FIELDS]; /* missing event fields bitmap */ |
| 902 | } extended; |
| 903 | } v; |
| 904 | }; |
| 905 | ... |
| 906 | } |
| 907 | |
| 908 | 6.3 Event Payload |
| 909 | |
| 910 | An event payload contains fields specific to a given event type. The fields |
| 911 | belonging to an event type are described in the event-specific meta-data |
| 912 | within a structure type. |
| 913 | |
| 914 | 6.3.1 Padding |
| 915 | |
| 916 | No padding at the end of the event payload. This differs from the ISO/C standard |
| 917 | for structures, but follows the CTF standard for structures. In a trace, even |
| 918 | though it makes sense to align the beginning of a structure, it really makes no |
| 919 | sense to add padding at the end of the structure, because structures are usually |
| 920 | not followed by a structure of the same type. |
| 921 | |
| 922 | This trick can be done by adding a zero-length "end" field at the end of the C |
| 923 | structures, and by using the offset of this field rather than using sizeof() |
| 924 | when calculating the size of a structure (see Appendix "A. Helper macros"). |
| 925 | |
| 926 | 6.3.2 Alignment |
| 927 | |
| 928 | The event payload is aligned on the largest alignment required by types |
| 929 | contained within the payload. (This follows the ISO/C standard for structures) |
| 930 | |
| 931 | |
| 932 | 7. Trace Stream Description Language (TSDL) |
| 933 | |
| 934 | The Trace Stream Description Language (TSDL) allows expression of the |
| 935 | binary trace streams layout in a C99-like Domain Specific Language |
| 936 | (DSL). |
| 937 | |
| 938 | |
| 939 | 7.1 Meta-data |
| 940 | |
| 941 | The trace stream layout description is located in the trace meta-data. |
| 942 | The meta-data is itself located in a stream identified by its name: |
| 943 | "metadata". |
| 944 | |
| 945 | The meta-data description can be expressed in two different formats: |
| 946 | text-only and packet-based. The text-only description facilitates |
| 947 | generation of meta-data and provides a convenient way to enter the |
| 948 | meta-data information by hand. The packet-based meta-data provides the |
| 949 | CTF stream packet facilities (checksumming, compression, encryption, |
| 950 | network-readiness) for meta-data stream generated and transported by a |
| 951 | tracer. |
| 952 | |
| 953 | The text-only meta-data file is a plain-text TSDL description. This file |
| 954 | must begin with the following characters to identify the file as a CTF |
| 955 | TSDL text-based metadata file (without the double-quotes) : |
| 956 | |
| 957 | "/* CTF" |
| 958 | |
| 959 | It must be followed by a space, and the version of the specification |
| 960 | followed by the CTF trace, e.g.: |
| 961 | |
| 962 | " 1.8" |
| 963 | |
| 964 | These characters allow automated discovery of file type and CTF |
| 965 | specification version. They are interpreted as a the beginning of a |
| 966 | comment by the TSDL metadata parser. The comment can be continued to |
| 967 | contain extra commented characters before it is closed. |
| 968 | |
| 969 | The packet-based meta-data is made of "meta-data packets", which each |
| 970 | start with a meta-data packet header. The packet-based meta-data |
| 971 | description is detected by reading the magic number "0x75D11D57" at the |
| 972 | beginning of the file. This magic number is also used to detect the |
| 973 | endianness of the architecture by trying to read the CTF magic number |
| 974 | and its counterpart in reversed endianness. The events within the |
| 975 | meta-data stream have no event header nor event context. Each event only |
| 976 | contains a "sequence" payload, which is a sequence of bits using the |
| 977 | "trace.packet.header.content_size" field as a placeholder for its length |
| 978 | (the packet header size should be substracted). The formatting of this |
| 979 | sequence of bits is a plain-text representation of the TSDL description. |
| 980 | Each meta-data packet start with a special packet header, specific to |
| 981 | the meta-data stream, which contains, exactly: |
| 982 | |
| 983 | struct metadata_packet_header { |
| 984 | uint32_t magic; /* 0x75D11D57 */ |
| 985 | uint8_t uuid[16]; /* Unique Universal Identifier */ |
| 986 | uint32_t checksum; /* 0 if unused */ |
| 987 | uint32_t content_size; /* in bits */ |
| 988 | uint32_t packet_size; /* in bits */ |
| 989 | uint8_t compression_scheme; /* 0 if unused */ |
| 990 | uint8_t encryption_scheme; /* 0 if unused */ |
| 991 | uint8_t checksum_scheme; /* 0 if unused */ |
| 992 | uint8_t major; /* CTF spec version major number */ |
| 993 | uint8_t minor; /* CTF spec version minor number */ |
| 994 | }; |
| 995 | |
| 996 | The packet-based meta-data can be converted to a text-only meta-data by |
| 997 | concatenating all the strings in contains. |
| 998 | |
| 999 | In the textual representation of the meta-data, the text contained |
| 1000 | within "/*" and "*/", as well as within "//" and end of line, are |
| 1001 | treated as comments. Boolean values can be represented as true, TRUE, |
| 1002 | or 1 for true, and false, FALSE, or 0 for false. Within the string-based |
| 1003 | meta-data description, the trace UUID is represented as a string of |
| 1004 | hexadecimal digits and dashes "-". In the event packet header, the trace |
| 1005 | UUID is represented as an array of bytes. |
| 1006 | |
| 1007 | |
| 1008 | 7.2 Declaration vs Definition |
| 1009 | |
| 1010 | A declaration associates a layout to a type, without specifying where |
| 1011 | this type is located in the event structure hierarchy (see Section 6). |
| 1012 | This therefore includes typedef, typealias, as well as all type |
| 1013 | specifiers. In certain circumstances (typedef, structure field and |
| 1014 | variant field), a declaration is followed by a declarator, which specify |
| 1015 | the newly defined type name (for typedef), or the field name (for |
| 1016 | declarations located within structure and variants). Array and sequence, |
| 1017 | declared with square brackets ("[" "]"), are part of the declarator, |
| 1018 | similarly to C99. The enumeration base type is specified by |
| 1019 | ": enum_base", which is part of the type specifier. The variant tag |
| 1020 | name, specified between "<" ">", is also part of the type specifier. |
| 1021 | |
| 1022 | A definition associates a type to a location in the event structure |
| 1023 | hierarchy (see Section 6). This association is denoted by ":=", as shown |
| 1024 | in Section 7.3. |
| 1025 | |
| 1026 | |
| 1027 | 7.3 TSDL Scopes |
| 1028 | |
| 1029 | TSDL uses three different types of scoping: a lexical scope is used for |
| 1030 | declarations and type definitions, and static and dynamic scopes are |
| 1031 | used for variants references to tag fields (with relative and absolute |
| 1032 | path lookups) and for sequence references to length fields. |
| 1033 | |
| 1034 | 7.3.1 Lexical Scope |
| 1035 | |
| 1036 | Each of "trace", "env", "stream", "event", "struct" and "variant" have |
| 1037 | their own nestable declaration scope, within which types can be declared |
| 1038 | using "typedef" and "typealias". A root declaration scope also contains |
| 1039 | all declarations located outside of any of the aforementioned |
| 1040 | declarations. An inner declaration scope can refer to type declared |
| 1041 | within its container lexical scope prior to the inner declaration scope. |
| 1042 | Redefinition of a typedef or typealias is not valid, although hiding an |
| 1043 | upper scope typedef or typealias is allowed within a sub-scope. |
| 1044 | |
| 1045 | 7.3.2 Static and Dynamic Scopes |
| 1046 | |
| 1047 | A local static scope consists in the scope generated by the declaration |
| 1048 | of fields within a compound type. A static scope is a local static scope |
| 1049 | augmented with the nested sub-static-scopes it contains. |
| 1050 | |
| 1051 | A dynamic scope consists in the static scope augmented with the |
| 1052 | implicit event structure definition hierarchy presented at Section 6. |
| 1053 | |
| 1054 | Multiple declarations of the same field name within a local static scope |
| 1055 | is not valid. It is however valid to re-use the same field name in |
| 1056 | different local scopes. |
| 1057 | |
| 1058 | Nested static and dynamic scopes form lookup paths. These are used for |
| 1059 | variant tag and sequence length references. They are used at the variant |
| 1060 | and sequence definition site to look up the location of the tag field |
| 1061 | associated with a variant, and to lookup up the location of the length |
| 1062 | field associated with a sequence. |
| 1063 | |
| 1064 | Variants and sequences can refer to a tag field either using a relative |
| 1065 | path or an absolute path. The relative path is relative to the scope in |
| 1066 | which the variant or sequence performing the lookup is located. |
| 1067 | Relative paths are only allowed to lookup within the same static scope, |
| 1068 | which includes its nested static scopes. Lookups targeting parent static |
| 1069 | scopes need to be performed with an absolute path. |
| 1070 | |
| 1071 | Absolute path lookups use the full path including the dynamic scope |
| 1072 | followed by a "." and then the static scope. Therefore, variants (or |
| 1073 | sequences) in lower levels in the dynamic scope (e.g. event context) can |
| 1074 | refer to a tag (or length) field located in upper levels (e.g. in the |
| 1075 | event header) by specifying, in this case, the associated tag with |
| 1076 | <stream.event.header.field_name>. This allows, for instance, the event |
| 1077 | context to define a variant referring to the "id" field of the event |
| 1078 | header as selector. |
| 1079 | |
| 1080 | The dynamic scope prefixes are thus: |
| 1081 | |
| 1082 | - Trace Environment: <env. >, |
| 1083 | - Trace Packet Header: <trace.packet.header. >, |
| 1084 | - Stream Packet Context: <stream.packet.context. >, |
| 1085 | - Event Header: <stream.event.header. >, |
| 1086 | - Stream Event Context: <stream.event.context. >, |
| 1087 | - Event Context: <event.context. >, |
| 1088 | - Event Payload: <event.fields. >. |
| 1089 | |
| 1090 | |
| 1091 | The target dynamic scope must be specified explicitly when referring to |
| 1092 | a field outside of the static scope (absolute scope reference). No |
| 1093 | conflict can occur between relative and dynamic paths, because the |
| 1094 | keywords "trace", "stream", and "event" are reserved, and thus |
| 1095 | not permitted as field names. It is recommended that field names |
| 1096 | clashing with CTF and C99 reserved keywords use an underscore prefix to |
| 1097 | eliminate the risk of generating a description containing an invalid |
| 1098 | field name. Consequently, fields starting with an underscore should have |
| 1099 | their leading underscore removed by the CTF trace readers. |
| 1100 | |
| 1101 | |
| 1102 | The information available in the dynamic scopes can be thought of as the |
| 1103 | current tracing context. At trace production, information about the |
| 1104 | current context is saved into the specified scope field levels. At trace |
| 1105 | consumption, for each event, the current trace context is therefore |
| 1106 | readable by accessing the upper dynamic scopes. |
| 1107 | |
| 1108 | |
| 1109 | 7.4 TSDL Examples |
| 1110 | |
| 1111 | The grammar representing the TSDL meta-data is presented in Appendix C. |
| 1112 | TSDL Grammar. This section presents a rather lighter reading that |
| 1113 | consists in examples of TSDL meta-data, with template values. |
| 1114 | |
| 1115 | The stream "id" can be left out if there is only one stream in the |
| 1116 | trace. The event "id" field can be left out if there is only one event |
| 1117 | in a stream. |
| 1118 | |
| 1119 | trace { |
| 1120 | major = value; /* CTF spec version major number */ |
| 1121 | minor = value; /* CTF spec version minor number */ |
| 1122 | uuid = "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; /* Trace UUID */ |
| 1123 | byte_order = be OR le; /* Endianness (required) */ |
| 1124 | packet.header := struct { |
| 1125 | uint32_t magic; |
| 1126 | uint8_t uuid[16]; |
| 1127 | uint32_t stream_id; |
| 1128 | }; |
| 1129 | }; |
| 1130 | |
| 1131 | /* |
| 1132 | * The "env" (environment) scope contains assignment expressions. The |
| 1133 | * field names and content are implementation-defined. |
| 1134 | */ |
| 1135 | env { |
| 1136 | pid = value; /* example */ |
| 1137 | proc_name = "name"; /* example */ |
| 1138 | ... |
| 1139 | }; |
| 1140 | |
| 1141 | stream { |
| 1142 | id = stream_id; |
| 1143 | /* Type 1 - Few event IDs; Type 2 - Many event IDs. See section 6.1. */ |
| 1144 | event.header := event_header_1 OR event_header_2; |
| 1145 | event.context := struct { |
| 1146 | ... |
| 1147 | }; |
| 1148 | packet.context := struct { |
| 1149 | ... |
| 1150 | }; |
| 1151 | }; |
| 1152 | |
| 1153 | event { |
| 1154 | name = "event_name"; |
| 1155 | id = value; /* Numeric identifier within the stream */ |
| 1156 | stream_id = stream_id; |
| 1157 | loglevel = value; |
| 1158 | context := struct { |
| 1159 | ... |
| 1160 | }; |
| 1161 | fields := struct { |
| 1162 | ... |
| 1163 | }; |
| 1164 | }; |
| 1165 | |
| 1166 | /* More detail on types in section 4. Types */ |
| 1167 | |
| 1168 | /* |
| 1169 | * Named types: |
| 1170 | * |
| 1171 | * Type declarations behave similarly to the C standard. |
| 1172 | */ |
| 1173 | |
| 1174 | typedef aliased_type_specifiers new_type_declarators; |
| 1175 | |
| 1176 | /* e.g.: typedef struct example new_type_name[10]; */ |
| 1177 | |
| 1178 | /* |
| 1179 | * typealias |
| 1180 | * |
| 1181 | * The "typealias" declaration can be used to give a name (including |
| 1182 | * pointer declarator specifier) to a type. It should also be used to |
| 1183 | * map basic C types (float, int, unsigned long, ...) to a CTF type. |
| 1184 | * Typealias is a superset of "typedef": it also allows assignment of a |
| 1185 | * simple variable identifier to a type. |
| 1186 | */ |
| 1187 | |
| 1188 | typealias type_class { |
| 1189 | ... |
| 1190 | } := type_specifiers type_declarator; |
| 1191 | |
| 1192 | /* |
| 1193 | * e.g.: |
| 1194 | * typealias integer { |
| 1195 | * size = 32; |
| 1196 | * align = 32; |
| 1197 | * signed = false; |
| 1198 | * } := struct page *; |
| 1199 | * |
| 1200 | * typealias integer { |
| 1201 | * size = 32; |
| 1202 | * align = 32; |
| 1203 | * signed = true; |
| 1204 | * } := int; |
| 1205 | */ |
| 1206 | |
| 1207 | struct name { |
| 1208 | ... |
| 1209 | }; |
| 1210 | |
| 1211 | variant name { |
| 1212 | ... |
| 1213 | }; |
| 1214 | |
| 1215 | enum name : integer_type { |
| 1216 | ... |
| 1217 | }; |
| 1218 | |
| 1219 | |
| 1220 | /* |
| 1221 | * Unnamed types, contained within compound type fields, typedef or typealias. |
| 1222 | */ |
| 1223 | |
| 1224 | struct { |
| 1225 | ... |
| 1226 | } |
| 1227 | |
| 1228 | struct { |
| 1229 | ... |
| 1230 | } align(value) |
| 1231 | |
| 1232 | variant { |
| 1233 | ... |
| 1234 | } |
| 1235 | |
| 1236 | enum : integer_type { |
| 1237 | ... |
| 1238 | } |
| 1239 | |
| 1240 | typedef type new_type[length]; |
| 1241 | |
| 1242 | struct { |
| 1243 | type field_name[length]; |
| 1244 | } |
| 1245 | |
| 1246 | typedef type new_type[length_type]; |
| 1247 | |
| 1248 | struct { |
| 1249 | type field_name[length_type]; |
| 1250 | } |
| 1251 | |
| 1252 | integer { |
| 1253 | ... |
| 1254 | } |
| 1255 | |
| 1256 | floating_point { |
| 1257 | ... |
| 1258 | } |
| 1259 | |
| 1260 | struct { |
| 1261 | integer_type field_name:size; /* GNU/C bitfield */ |
| 1262 | } |
| 1263 | |
| 1264 | struct { |
| 1265 | string field_name; |
| 1266 | } |
| 1267 | |
| 1268 | |
| 1269 | 8. Clocks |
| 1270 | |
| 1271 | Clock metadata allows to describe the clock topology of the system, as |
| 1272 | well as to detail each clock parameter. In absence of clock description, |
| 1273 | it is assumed that all fields named "timestamp" use the same clock |
| 1274 | source, which increments once per nanosecond. |
| 1275 | |
| 1276 | Describing a clock and how it is used by streams is threefold: first, |
| 1277 | the clock and clock topology should be described in a "clock" |
| 1278 | description block, e.g.: |
| 1279 | |
| 1280 | clock { |
| 1281 | name = cycle_counter_sync; |
| 1282 | uuid = "62189bee-96dc-11e0-91a8-cfa3d89f3923"; |
| 1283 | description = "Cycle counter synchronized across CPUs"; |
| 1284 | freq = 1000000000; /* frequency, in Hz */ |
| 1285 | /* precision in seconds is: 1000 * (1/freq) */ |
| 1286 | precision = 1000; |
| 1287 | /* |
| 1288 | * clock value offset from Epoch is: |
| 1289 | * offset_s + (offset * (1/freq)) |
| 1290 | */ |
| 1291 | offset_s = 1326476837; |
| 1292 | offset = 897235420; |
| 1293 | absolute = FALSE; |
| 1294 | }; |
| 1295 | |
| 1296 | The mandatory "name" field specifies the name of the clock identifier, |
| 1297 | which can later be used as a reference. The optional field "uuid" is the |
| 1298 | unique identifier of the clock. It can be used to correlate different |
| 1299 | traces that use the same clock. An optional textual description string |
| 1300 | can be added with the "description" field. The "freq" field is the |
| 1301 | initial frequency of the clock, in Hz. If the "freq" field is not |
| 1302 | present, the frequency is assumed to be 1000000000 (providing clock |
| 1303 | increment of 1 ns). The optional "precision" field details the |
| 1304 | uncertainty on the clock measurements, in (1/freq) units. The "offset_s" |
| 1305 | and "offset" fields indicate the offset from POSIX.1 Epoch, 1970-01-01 |
| 1306 | 00:00:00 +0000 (UTC), to the zero of value of the clock. The "offset_s" |
| 1307 | field is in seconds. The "offset" field is in (1/freq) units. If any of |
| 1308 | the "offset_s" or "offset" field is not present, it is assigned the 0 |
| 1309 | value. The field "absolute" is TRUE if the clock is a global reference |
| 1310 | across different clock uuid (e.g. NTP time). Otherwise, "absolute" is |
| 1311 | FALSE, and the clock can be considered as synchronized only with other |
| 1312 | clocks that have the same uuid. |
| 1313 | |
| 1314 | |
| 1315 | Secondly, a reference to this clock should be added within an integer |
| 1316 | type: |
| 1317 | |
| 1318 | typealias integer { |
| 1319 | size = 64; align = 1; signed = false; |
| 1320 | map = clock.cycle_counter_sync.value; |
| 1321 | } := uint64_ccnt_t; |
| 1322 | |
| 1323 | Thirdly, stream declarations can reference the clock they use as a |
| 1324 | time-stamp source: |
| 1325 | |
| 1326 | struct packet_context { |
| 1327 | uint64_ccnt_t ccnt_begin; |
| 1328 | uint64_ccnt_t ccnt_end; |
| 1329 | /* ... */ |
| 1330 | }; |
| 1331 | |
| 1332 | stream { |
| 1333 | /* ... */ |
| 1334 | event.header := struct { |
| 1335 | uint64_ccnt_t timestamp; |
| 1336 | /* ... */ |
| 1337 | } |
| 1338 | packet.context := struct packet_context; |
| 1339 | }; |
| 1340 | |
| 1341 | For a N-bit integer type referring to a clock, if the integer overflows |
| 1342 | compared to the N low order bits of the clock prior value, then it is |
| 1343 | assumed that one, and only one, overflow occurred. It is therefore |
| 1344 | important that events encoding time on a small number of bits happen |
| 1345 | frequently enough to detect when more than one N-bit overflow occurs. |
| 1346 | |
| 1347 | In a packet context, clock field names ending with "_begin" and "_end" |
| 1348 | have a special meaning: this refers to the time-stamps at, respectively, |
| 1349 | the beginning and the end of each packet. |
| 1350 | |
| 1351 | |
| 1352 | A. Helper macros |
| 1353 | |
| 1354 | The two following macros keep track of the size of a GNU/C structure without |
| 1355 | padding at the end by placing HEADER_END as the last field. A one byte end field |
| 1356 | is used for C90 compatibility (C99 flexible arrays could be used here). Note |
| 1357 | that this does not affect the effective structure size, which should always be |
| 1358 | calculated with the header_sizeof() helper. |
| 1359 | |
| 1360 | #define HEADER_END char end_field |
| 1361 | #define header_sizeof(type) offsetof(typeof(type), end_field) |
| 1362 | |
| 1363 | |
| 1364 | B. Stream Header Rationale |
| 1365 | |
| 1366 | An event stream is divided in contiguous event packets of variable size. These |
| 1367 | subdivisions allow the trace analyzer to perform a fast binary search by time |
| 1368 | within the stream (typically requiring to index only the event packet headers) |
| 1369 | without reading the whole stream. These subdivisions have a variable size to |
| 1370 | eliminate the need to transfer the event packet padding when partially filled |
| 1371 | event packets must be sent when streaming a trace for live viewing/analysis. |
| 1372 | An event packet can contain a certain amount of padding at the end. Dividing |
| 1373 | streams into event packets is also useful for network streaming over UDP and |
| 1374 | flight recorder mode tracing (a whole event packet can be swapped out of the |
| 1375 | buffer atomically for reading). |
| 1376 | |
| 1377 | The stream header is repeated at the beginning of each event packet to allow |
| 1378 | flexibility in terms of: |
| 1379 | |
| 1380 | - streaming support, |
| 1381 | - allowing arbitrary buffers to be discarded without making the trace |
| 1382 | unreadable, |
| 1383 | - allow UDP packet loss handling by either dealing with missing event packet |
| 1384 | or asking for re-transmission. |
| 1385 | - transparently support flight recorder mode, |
| 1386 | - transparently support crash dump. |
| 1387 | |
| 1388 | |
| 1389 | C. TSDL Grammar |
| 1390 | |
| 1391 | /* |
| 1392 | * Common Trace Format (CTF) Trace Stream Description Language (TSDL) Grammar. |
| 1393 | * |
| 1394 | * Inspired from the C99 grammar: |
| 1395 | * http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf (Annex A) |
| 1396 | * and c++1x grammar (draft) |
| 1397 | * http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3291.pdf (Annex A) |
| 1398 | * |
| 1399 | * Specialized for CTF needs by including only constant and declarations from |
| 1400 | * C99 (excluding function declarations), and by adding support for variants, |
| 1401 | * sequences and CTF-specific specifiers. Enumeration container types |
| 1402 | * semantic is inspired from c++1x enum-base. |
| 1403 | */ |
| 1404 | |
| 1405 | 1) Lexical grammar |
| 1406 | |
| 1407 | 1.1) Lexical elements |
| 1408 | |
| 1409 | token: |
| 1410 | keyword |
| 1411 | identifier |
| 1412 | constant |
| 1413 | string-literal |
| 1414 | punctuator |
| 1415 | |
| 1416 | 1.2) Keywords |
| 1417 | |
| 1418 | keyword: is one of |
| 1419 | |
| 1420 | align |
| 1421 | const |
| 1422 | char |
| 1423 | clock |
| 1424 | double |
| 1425 | enum |
| 1426 | env |
| 1427 | event |
| 1428 | floating_point |
| 1429 | float |
| 1430 | integer |
| 1431 | int |
| 1432 | long |
| 1433 | short |
| 1434 | signed |
| 1435 | stream |
| 1436 | string |
| 1437 | struct |
| 1438 | trace |
| 1439 | typealias |
| 1440 | typedef |
| 1441 | unsigned |
| 1442 | variant |
| 1443 | void |
| 1444 | _Bool |
| 1445 | _Complex |
| 1446 | _Imaginary |
| 1447 | |
| 1448 | |
| 1449 | 1.3) Identifiers |
| 1450 | |
| 1451 | identifier: |
| 1452 | identifier-nondigit |
| 1453 | identifier identifier-nondigit |
| 1454 | identifier digit |
| 1455 | |
| 1456 | identifier-nondigit: |
| 1457 | nondigit |
| 1458 | universal-character-name |
| 1459 | any other implementation-defined characters |
| 1460 | |
| 1461 | nondigit: |
| 1462 | _ |
| 1463 | [a-zA-Z] /* regular expression */ |
| 1464 | |
| 1465 | digit: |
| 1466 | [0-9] /* regular expression */ |
| 1467 | |
| 1468 | 1.4) Universal character names |
| 1469 | |
| 1470 | universal-character-name: |
| 1471 | \u hex-quad |
| 1472 | \U hex-quad hex-quad |
| 1473 | |
| 1474 | hex-quad: |
| 1475 | hexadecimal-digit hexadecimal-digit hexadecimal-digit hexadecimal-digit |
| 1476 | |
| 1477 | 1.5) Constants |
| 1478 | |
| 1479 | constant: |
| 1480 | integer-constant |
| 1481 | enumeration-constant |
| 1482 | character-constant |
| 1483 | |
| 1484 | integer-constant: |
| 1485 | decimal-constant integer-suffix-opt |
| 1486 | octal-constant integer-suffix-opt |
| 1487 | hexadecimal-constant integer-suffix-opt |
| 1488 | |
| 1489 | decimal-constant: |
| 1490 | nonzero-digit |
| 1491 | decimal-constant digit |
| 1492 | |
| 1493 | octal-constant: |
| 1494 | 0 |
| 1495 | octal-constant octal-digit |
| 1496 | |
| 1497 | hexadecimal-constant: |
| 1498 | hexadecimal-prefix hexadecimal-digit |
| 1499 | hexadecimal-constant hexadecimal-digit |
| 1500 | |
| 1501 | hexadecimal-prefix: |
| 1502 | 0x |
| 1503 | 0X |
| 1504 | |
| 1505 | nonzero-digit: |
| 1506 | [1-9] |
| 1507 | |
| 1508 | integer-suffix: |
| 1509 | unsigned-suffix long-suffix-opt |
| 1510 | unsigned-suffix long-long-suffix |
| 1511 | long-suffix unsigned-suffix-opt |
| 1512 | long-long-suffix unsigned-suffix-opt |
| 1513 | |
| 1514 | unsigned-suffix: |
| 1515 | u |
| 1516 | U |
| 1517 | |
| 1518 | long-suffix: |
| 1519 | l |
| 1520 | L |
| 1521 | |
| 1522 | long-long-suffix: |
| 1523 | ll |
| 1524 | LL |
| 1525 | |
| 1526 | enumeration-constant: |
| 1527 | identifier |
| 1528 | string-literal |
| 1529 | |
| 1530 | character-constant: |
| 1531 | ' c-char-sequence ' |
| 1532 | L' c-char-sequence ' |
| 1533 | |
| 1534 | c-char-sequence: |
| 1535 | c-char |
| 1536 | c-char-sequence c-char |
| 1537 | |
| 1538 | c-char: |
| 1539 | any member of source charset except single-quote ('), backslash |
| 1540 | (\), or new-line character. |
| 1541 | escape-sequence |
| 1542 | |
| 1543 | escape-sequence: |
| 1544 | simple-escape-sequence |
| 1545 | octal-escape-sequence |
| 1546 | hexadecimal-escape-sequence |
| 1547 | universal-character-name |
| 1548 | |
| 1549 | simple-escape-sequence: one of |
| 1550 | \' \" \? \\ \a \b \f \n \r \t \v |
| 1551 | |
| 1552 | octal-escape-sequence: |
| 1553 | \ octal-digit |
| 1554 | \ octal-digit octal-digit |
| 1555 | \ octal-digit octal-digit octal-digit |
| 1556 | |
| 1557 | hexadecimal-escape-sequence: |
| 1558 | \x hexadecimal-digit |
| 1559 | hexadecimal-escape-sequence hexadecimal-digit |
| 1560 | |
| 1561 | 1.6) String literals |
| 1562 | |
| 1563 | string-literal: |
| 1564 | " s-char-sequence-opt " |
| 1565 | L" s-char-sequence-opt " |
| 1566 | |
| 1567 | s-char-sequence: |
| 1568 | s-char |
| 1569 | s-char-sequence s-char |
| 1570 | |
| 1571 | s-char: |
| 1572 | any member of source charset except double-quote ("), backslash |
| 1573 | (\), or new-line character. |
| 1574 | escape-sequence |
| 1575 | |
| 1576 | 1.7) Punctuators |
| 1577 | |
| 1578 | punctuator: one of |
| 1579 | [ ] ( ) { } . -> * + - < > : ; ... = , |
| 1580 | |
| 1581 | |
| 1582 | 2) Phrase structure grammar |
| 1583 | |
| 1584 | primary-expression: |
| 1585 | identifier |
| 1586 | constant |
| 1587 | string-literal |
| 1588 | ( unary-expression ) |
| 1589 | |
| 1590 | postfix-expression: |
| 1591 | primary-expression |
| 1592 | postfix-expression [ unary-expression ] |
| 1593 | postfix-expression . identifier |
| 1594 | postfix-expressoin -> identifier |
| 1595 | |
| 1596 | unary-expression: |
| 1597 | postfix-expression |
| 1598 | unary-operator postfix-expression |
| 1599 | |
| 1600 | unary-operator: one of |
| 1601 | + - |
| 1602 | |
| 1603 | assignment-operator: |
| 1604 | = |
| 1605 | |
| 1606 | type-assignment-operator: |
| 1607 | := |
| 1608 | |
| 1609 | constant-expression-range: |
| 1610 | unary-expression ... unary-expression |
| 1611 | |
| 1612 | 2.2) Declarations: |
| 1613 | |
| 1614 | declaration: |
| 1615 | declaration-specifiers declarator-list-opt ; |
| 1616 | ctf-specifier ; |
| 1617 | |
| 1618 | declaration-specifiers: |
| 1619 | storage-class-specifier declaration-specifiers-opt |
| 1620 | type-specifier declaration-specifiers-opt |
| 1621 | type-qualifier declaration-specifiers-opt |
| 1622 | |
| 1623 | declarator-list: |
| 1624 | declarator |
| 1625 | declarator-list , declarator |
| 1626 | |
| 1627 | abstract-declarator-list: |
| 1628 | abstract-declarator |
| 1629 | abstract-declarator-list , abstract-declarator |
| 1630 | |
| 1631 | storage-class-specifier: |
| 1632 | typedef |
| 1633 | |
| 1634 | type-specifier: |
| 1635 | void |
| 1636 | char |
| 1637 | short |
| 1638 | int |
| 1639 | long |
| 1640 | float |
| 1641 | double |
| 1642 | signed |
| 1643 | unsigned |
| 1644 | _Bool |
| 1645 | _Complex |
| 1646 | _Imaginary |
| 1647 | struct-specifier |
| 1648 | variant-specifier |
| 1649 | enum-specifier |
| 1650 | typedef-name |
| 1651 | ctf-type-specifier |
| 1652 | |
| 1653 | align-attribute: |
| 1654 | align ( unary-expression ) |
| 1655 | |
| 1656 | struct-specifier: |
| 1657 | struct identifier-opt { struct-or-variant-declaration-list-opt } align-attribute-opt |
| 1658 | struct identifier align-attribute-opt |
| 1659 | |
| 1660 | struct-or-variant-declaration-list: |
| 1661 | struct-or-variant-declaration |
| 1662 | struct-or-variant-declaration-list struct-or-variant-declaration |
| 1663 | |
| 1664 | struct-or-variant-declaration: |
| 1665 | specifier-qualifier-list struct-or-variant-declarator-list ; |
| 1666 | declaration-specifiers-opt storage-class-specifier declaration-specifiers-opt declarator-list ; |
| 1667 | typealias declaration-specifiers abstract-declarator-list type-assignment-operator declaration-specifiers abstract-declarator-list ; |
| 1668 | typealias declaration-specifiers abstract-declarator-list type-assignment-operator declarator-list ; |
| 1669 | |
| 1670 | specifier-qualifier-list: |
| 1671 | type-specifier specifier-qualifier-list-opt |
| 1672 | type-qualifier specifier-qualifier-list-opt |
| 1673 | |
| 1674 | struct-or-variant-declarator-list: |
| 1675 | struct-or-variant-declarator |
| 1676 | struct-or-variant-declarator-list , struct-or-variant-declarator |
| 1677 | |
| 1678 | struct-or-variant-declarator: |
| 1679 | declarator |
| 1680 | declarator-opt : unary-expression |
| 1681 | |
| 1682 | variant-specifier: |
| 1683 | variant identifier-opt variant-tag-opt { struct-or-variant-declaration-list } |
| 1684 | variant identifier variant-tag |
| 1685 | |
| 1686 | variant-tag: |
| 1687 | < unary-expression > |
| 1688 | |
| 1689 | enum-specifier: |
| 1690 | enum identifier-opt { enumerator-list } |
| 1691 | enum identifier-opt { enumerator-list , } |
| 1692 | enum identifier |
| 1693 | enum identifier-opt : declaration-specifiers { enumerator-list } |
| 1694 | enum identifier-opt : declaration-specifiers { enumerator-list , } |
| 1695 | |
| 1696 | enumerator-list: |
| 1697 | enumerator |
| 1698 | enumerator-list , enumerator |
| 1699 | |
| 1700 | enumerator: |
| 1701 | enumeration-constant |
| 1702 | enumeration-constant assignment-operator unary-expression |
| 1703 | enumeration-constant assignment-operator constant-expression-range |
| 1704 | |
| 1705 | type-qualifier: |
| 1706 | const |
| 1707 | |
| 1708 | declarator: |
| 1709 | pointer-opt direct-declarator |
| 1710 | |
| 1711 | direct-declarator: |
| 1712 | identifier |
| 1713 | ( declarator ) |
| 1714 | direct-declarator [ unary-expression ] |
| 1715 | |
| 1716 | abstract-declarator: |
| 1717 | pointer-opt direct-abstract-declarator |
| 1718 | |
| 1719 | direct-abstract-declarator: |
| 1720 | identifier-opt |
| 1721 | ( abstract-declarator ) |
| 1722 | direct-abstract-declarator [ unary-expression ] |
| 1723 | direct-abstract-declarator [ ] |
| 1724 | |
| 1725 | pointer: |
| 1726 | * type-qualifier-list-opt |
| 1727 | * type-qualifier-list-opt pointer |
| 1728 | |
| 1729 | type-qualifier-list: |
| 1730 | type-qualifier |
| 1731 | type-qualifier-list type-qualifier |
| 1732 | |
| 1733 | typedef-name: |
| 1734 | identifier |
| 1735 | |
| 1736 | 2.3) CTF-specific declarations |
| 1737 | |
| 1738 | ctf-specifier: |
| 1739 | clock { ctf-assignment-expression-list-opt } |
| 1740 | event { ctf-assignment-expression-list-opt } |
| 1741 | stream { ctf-assignment-expression-list-opt } |
| 1742 | env { ctf-assignment-expression-list-opt } |
| 1743 | trace { ctf-assignment-expression-list-opt } |
| 1744 | typealias declaration-specifiers abstract-declarator-list type-assignment-operator declaration-specifiers abstract-declarator-list |
| 1745 | typealias declaration-specifiers abstract-declarator-list type-assignment-operator declarator-list |
| 1746 | |
| 1747 | ctf-type-specifier: |
| 1748 | floating_point { ctf-assignment-expression-list-opt } |
| 1749 | integer { ctf-assignment-expression-list-opt } |
| 1750 | string { ctf-assignment-expression-list-opt } |
| 1751 | string |
| 1752 | |
| 1753 | ctf-assignment-expression-list: |
| 1754 | ctf-assignment-expression ; |
| 1755 | ctf-assignment-expression-list ctf-assignment-expression ; |
| 1756 | |
| 1757 | ctf-assignment-expression: |
| 1758 | unary-expression assignment-operator unary-expression |
| 1759 | unary-expression type-assignment-operator type-specifier |
| 1760 | declaration-specifiers-opt storage-class-specifier declaration-specifiers-opt declarator-list |
| 1761 | typealias declaration-specifiers abstract-declarator-list type-assignment-operator declaration-specifiers abstract-declarator-list |
| 1762 | typealias declaration-specifiers abstract-declarator-list type-assignment-operator declarator-list |