Searched refs:conventions (Results 1 – 25 of 497) sorted by relevance
12345678910>>...20
| /third_party/vulkan-headers/registry/ |
| D | genvk.py | 139 conventions = APIConventions()
141 defaultAPIName = conventions.xml_api_name
153 conventions = conventions,
178 conventions = conventions,
196 conventions = conventions,
220 conventions = conventions,
240 conventions = conventions,
262 conventions = conventions,
281 conventions = conventions,
299 conventions = conventions,
[all …]
|
| D | generator.py | 112 conventions=None, argument
176 self.conventions = conventions
485 if self.genOpts.conventions.constFlagBits and groupElem.get('type') == 'bitmask':
706 self.conventions.generate_max_enum_in_docs):
780 self.genOpts.conventions.should_insert_may_alias_macro(self.genOpts)
793 self.conventions = genOpts.conventions
952 …if self.should_insert_may_alias_macro and self.genOpts.conventions.is_voidpointer_alias(elem.tag, …
954 tail = self.genOpts.conventions.make_voidpointer_alias(tail)
998 …if self.should_insert_may_alias_macro and self.genOpts.conventions.is_voidpointer_alias(elem.tag, …
1000 tail = self.genOpts.conventions.make_voidpointer_alias(tail)
[all …]
|
| /third_party/boost/libs/ptr_container/doc/ |
| D | comp_conventions.sh | 12 rst2html.py conventions.rst |
13 … external" href="compatible_smart_ptr.html"><em>compatible-smart-ptr</em></a>@g' > conventions.html
|
| /third_party/openGLES/extensions/ARB/ |
| D | ARB_fragment_coord_conventions.txt | 70 This extension provides alternative conventions for the fragment
75 Beyond the scope of this extension are coordinate conventions used
78 In the case of the coordinate conventions for rasterization and
81 arbitrary clip-space and window-space coordinate space conventions.
82 Adopting other clip-space and window-space conventions involves
104 Other window coordinate conventions exist for other rendering APIs.
120 or OpenGL assembly extensions to specify alternative conventions
150 depends on the fragment processing pixel-center and origin conventions
324 These options affect the fragment coordinate conventions specified
422 We use "conventions" because the extension provides two alternative
[all …]
|
| D | ARB_clip_control.txt | 69 conventions, and 2) potentially improve the numerical precision of the Z
95 in Direct3D, so no change relative to OpenGL conventions is needed there.
98 conventions. For example, the viewport rectangle in Direct3D needs to be
109 OpenGL FBO conventions would map (0,0) to the lower-left corner of the
122 Applications happy with OpenGL's origin conventions but seeking
323 We also note the possibility for other possible conventions.
549 origin conventions and subject asynchronous window resizes.
648 conventions once; for example, to match the Direct3D conventions.
662 conventions?
759 the Direct3D clip-space AND window-space conventions like this:
[all …]
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
| D | ARB_fragment_coord_conventions.txt | 60 This extension provides alternative conventions for the fragment
65 Beyond the scope of this extension are coordinate conventions used
68 In the case of the coordinate conventions for rasterization and
71 arbitrary clip-space and window-space coordinate space conventions.
72 Adopting other clip-space and window-space conventions involves
94 Other window coordinate conventions exist for other rendering APIs.
110 or OpenGL assembly extensions to specify alternative conventions
140 depends on the fragment processing pixel-center and origin conventions
314 These options affect the fragment coordinate conventions specified
412 We use "conventions" because the extension provides two alternative
[all …]
|
| D | ARB_clip_control.txt | 59 conventions, and 2) potentially improve the numerical precision of the Z
85 in Direct3D, so no change relative to OpenGL conventions is needed there.
88 conventions. For example, the viewport rectangle in Direct3D needs to be
99 OpenGL FBO conventions would map (0,0) to the lower-left corner of the
112 Applications happy with OpenGL's origin conventions but seeking
313 We also note the possibility for other possible conventions.
539 origin conventions and subject asynchronous window resizes.
638 conventions once; for example, to match the Direct3D conventions.
652 conventions?
749 the Direct3D clip-space AND window-space conventions like this:
[all …]
|
| /third_party/lz4/ |
| D | INSTALL | 9 LZ4's `Makefile` supports standard [Makefile conventions],
13 [Makefile conventions]: https://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html
|
| /third_party/boost/libs/geometry/doc/ |
| D | introduction.qbk | 36 The library follows existing conventions:
38 * conventions from boost
39 * conventions from the std library
40 * conventions and names from one of the __ogc__ standards on geometry and, more
|
| D | guidelines.qbk | 22 Generally, prefer style of modern C++, conventions as used in latest C++ standard
132 [heading Naming conventions]
161 [heading C++ use conventions]
169 [heading Specialisations and dispatching conventions]
|
| /third_party/boost/libs/math/doc/filters/ |
| D | daubechies.qbk | 38 Numerous notational conventions for the filter coefficients exist.
64 Mathematica conventions:
71 PyWavelet conventions:
85 For this reason, we demo some other conventions for the wavelet filter as well:
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/AVR/ |
| D | AVRCallingConv.td | 8 // This describes the calling conventions for AVR architecture.
35 // The calling conventions are implemented in custom C++ code
|
| /third_party/boost/libs/pool/doc/ |
| D | index.idx | 24 conventions
29 formatting conventions \<convention\w*\>
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/SystemZ/ |
| D | SystemZCallingConv.td | 1 //=- SystemZCallingConv.td - Calling conventions for SystemZ -*- tablegen -*-=//
8 // This describes the calling conventions for the SystemZ ABI.
61 // z/Linux argument calling conventions for GHC
84 // z/Linux argument calling conventions
|
| /third_party/pixman/ |
| D | arm-simd-test.S | 7 #error EABI is required (to be sure that calling conventions are compatible)
|
| D | neon-test.S | 9 #error EABI is required (to be sure that calling conventions are compatible)
|
| /third_party/vk-gl-cts/external/openglcts/ |
| D | CONTRIBUTING.md | 14 - [Coding conventions](#coding-conventions)
82 Coding conventions
|
| /third_party/boost/libs/proto/doc/ |
| D | getting_started.qbk | 12 [include conventions.qbk]
|
| /third_party/libffi/ |
| D | README.OpenSource | 8 …ovides a portable, high level programming interface to various calling conventions. This allows a …
|
| /third_party/openGLES/docs/ |
| D | GLSLExtensionRules.txt | 22 conventions for writing OpenGL extension specifications that extend the
32 we'd like to establish some name conventions to avoid name-space
51 Consequently, vendors must use the following naming conventions
137 the conventions of C/C++
148 Naming conventions for new data types defined by an extension
238 (A) is borrowed from C++ operator overloading conventions.
403 - summarized section 1 conventions on name decorations
|
| /third_party/skia/third_party/externals/opengl-registry/docs/ |
| D | GLSLExtensionRules.txt | 22 conventions for writing OpenGL extension specifications that extend the
32 we'd like to establish some name conventions to avoid name-space
51 Consequently, vendors must use the following naming conventions
137 the conventions of C/C++
148 Naming conventions for new data types defined by an extension
238 (A) is borrowed from C++ operator overloading conventions.
403 - summarized section 1 conventions on name decorations
|
| /third_party/python/Doc/library/ |
| D | i18n.rst | 10 conventions.
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/VE/ |
| D | VECallingConv.td | 9 // This describes the calling conventions for the VE architectures.
|
| /third_party/boost/libs/math/doc/overview/ |
| D | structure.qbk | 32 [section:conventions Document Conventions]
34 [indexterm1 conventions]
36 This documentation aims to use of the following naming and formatting conventions.
54 [endsect] [/section:conventions Document Conventions]
|
| /third_party/typescript_eslint/packages/eslint-plugin/docs/rules/ |
| D | naming-convention.md | 1 # Enforces naming conventions for everything across a codebase (`naming-convention`)
3 Enforcing naming conventions helps keep the codebase consistent, and reduces overhead when thinking…
6 …st of the time you needed 3 or more rules at once to enforce different conventions, hoping they di…
10 This rule allows you to enforce conventions for any identifier, using granular selectors to create …
426 ### Enforce the codebase follows ESLint's `camelcase` conventions
465 If you do not want to enforce naming conventions for anything.
|
12345678910>>...20