Searched refs:structures (Results 1 – 25 of 889) sorted by relevance
12345678910>>...36
4 structures = [] variable24 structures.append(X)29 for typ in structures:
20 The Vulkan 1.0 render pass creation sub-structures do not include23 with new extensible structures for passing additional subpass information.26 slink:VkInputAttachmentAspectReference structures that extended the original42 The details of these mappings are explained fully in the new structures.
22 The Vulkan 1.0 render pass creation sub-structures do not include25 with new extensible structures for passing additional subpass information.28 slink:VkInputAttachmentAspectReference structures that extended the original44 The details of these mappings are explained fully in the new structures.
24 The Vulkan 1.0 feature/limit/formatproperty structures do not include26 This extension wraps them in new structures with ptext:sType/ptext:pNext28 structures by constructing the chain and letting the implementation fill32 The new feature structure (and a pname:pNext chain of extending structures)
22 The Vulkan 1.0 feature/limit/formatproperty structures do not include24 This extension wraps them in new structures with ptext:sType/ptext:pNext26 structures by constructing the chain and letting the implementation fill30 The new feature structure (and a pname:pNext chain of extending structures)
24 slink:VkSparseImageMemoryRequirements structures do not include pname:sType26 This extension wraps them in new structures with these members, so an27 application can query a chain of memory requirements structures by
26 slink:VkSparseImageMemoryRequirements structures do not include pname:sType28 This extension wraps them in new structures with these members, so an29 application can query a chain of memory requirements structures by
60 Acceleration structures are the most common way to represent the geometry94 * reworked geometry structures so they could be better shared between111 The following is a more detailed comparision of which commands, structures,114 * Aliased functionality -- enums, structures, and commands that are138 * Changed enums, structures, and commands:188 * Added enums, structures and commands:271 acceleration structures295 enum to query sizes for acceleration structures and scratch storage333 * Allocate acceleration structures from stext:VkBuffers and add a mode to340 ** acceleration structures now take a slink:VkBuffer and offset at[all …]
60 Acceleration structures are the most common way to represent the geometry94 * reworked geometry structures so they could be better shared between111 The following is a more detailed comparison of which commands, structures,114 * Aliased functionality -- enums, structures, and commands that are138 * Changed enums, structures, and commands:188 * Added enums, structures and commands:271 acceleration structures295 enum to query sizes for acceleration structures and scratch storage333 * Allocate acceleration structures from stext:VkBuffers and add a mode to340 ** acceleration structures now take a slink:VkBuffer and offset at[all …]
34 guide says "`Structures which extend other structures through the37 three base structures (vkCmdBlitImage2KHR, vkCmdCopyImageToBuffer2KHR and39 Creating three identical structures with unique names seemed undesirable.
36 guide says "`Structures which extend other structures through the39 three base structures (vkCmdBlitImage2KHR, vkCmdCopyImageToBuffer2KHR and41 Creating three identical structures with unique names seemed undesirable.
25 7zItem.* - .7z structures99 2) call CrcGenerateTable(); function to initialize CRC structures.101 3) call SzArEx_Init(&db); function to initialize db structures.107 SzArEx_Open function allocates and frees temporary structures by "allocTemp" functions.156 Estimated size of one file structures in solid archive:161 - File Name (variable length) + pointer + allocation structures165 - Memory for LZMA decompressing structures
12 _Acceleration structures_ are data structures used by the implementation to16 (see <<resources-acceleration-structures,Acceleration Structures>>),20 There are two types of acceleration structures, _top level acceleration34 structures.66 The API defines two types of operations to produce acceleration structures99 Acceleration structures allow the use of particular input values to signal155 slink:VkAccelerationStructureInstanceKHR structures defining156 acceleration structures.157 This parameter must: be `NULL` for bottom level acceleration structures.259 To build acceleration structures call:[all …]
12 _Acceleration structures_ are data structures used by the implementation to16 (see <<resources-acceleration-structures,Acceleration Structures>>),20 There are two types of acceleration structures, _top level acceleration34 structures.66 The API defines two types of operations to produce acceleration structures140 Acceleration structures allow the use of particular input values to signal195 slink:VkAccelerationStructureInstanceKHR structures defining196 acceleration structures.197 This parameter must: be `NULL` for bottom level acceleration structures.302 To build acceleration structures call:[all …]
47 sname:VkCheckpointData2NV structures.53 return the variable is overwritten with the number of structures actually57 available, at most pname:pCheckpointDataCount structures will be written.106 sname:VkCheckpointDataNV structures.113 return the variable is overwritten with the number of structures actually117 available, at most pname:pCheckpointDataCount structures will be written.
50 sname:VkCheckpointData2NV structures.56 return the variable is overwritten with the number of structures actually60 available, at most pname:pCheckpointDataCount structures will be written.109 sname:VkCheckpointDataNV structures.116 return the variable is overwritten with the number of structures actually120 available, at most pname:pCheckpointDataCount structures will be written.
2 - Describes most data structures used in sparse.4 As far as the parsing structures go...18 As with the various other structures, it has some common data and a union of sub-structures for the…28 The linearized bytecode itself has a set of nested structures.52 That covers most of the major data structures in Sparse.
16 structures.h structures.c \
139 libmicrospdy_la-structures.lo libmicrospdy_la-internal.lo \391 structures.h structures.c \502 @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/libmicrospdy_la-structures.Plo@am__quote@549 libmicrospdy_la-structures.lo: structures.c550 …structures.lo -MD -MP -MF $(DEPDIR)/libmicrospdy_la-structures.Tpo -c -o libmicrospdy_la-structure…551 …RUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/libmicrospdy_la-structures.Tpo $(DEPDIR)/libmicrospdy_la-struct…554 …a_CFLAGS) $(CFLAGS) -c -o libmicrospdy_la-structures.lo `test -f 'structures.c' || echo '$(srcdir)…
8 All acceleration structures in pname:pAccelerationStructures must: have11 All acceleration structures in pname:pAccelerationStructures must: have
15 # structures are used.19 # data structures or functions. zlib (gz) is always required, bzip2 (bz2)
40 Here are some of the main data structures in the library.61 B<SSL> structures which are later created for the connections.73 links to mostly all other structures.80 containing the prototypes for the data structures and functions:
22 …t affect the current traversal. For some transformations of nested AST structures you may need to …48 * You take into account some less common AST structures, such as declarations inside a loop header.49 …structures that have already been pruned away for example, and on the other hand you can depend on…
43 Several OpenSSL structures can have application-specific data attached to them,45 The specific structures are:67 applications to use this facility for their own structures.70 structures. Since the application data can be anything at all it is passed78 unique within structures for the lifetime of the program. Applications141 are pointers to the destination and source B<CRYPTO_EX_DATA> structures,