Home
last modified time | relevance | path

Searched refs:macros (Results 1 – 25 of 74) sorted by relevance

123

/device/generic/vulkan-cereal/protocols/vulkan/config/
DREADME.adoc9 The macros in `spec-macros.rb` and `spec-macros/extension.rb` are described
42 * `spec-macros.rb` - custom asciidoctor macros used in spec markup
DREADME.md5 The macros in `vulkan-macros.rb` and `vulkan-macros/extension.rb` are
/device/generic/vulkan-cereal/protocols/vulkan/style/
Dmarkup.txt376 However, using the <<markup-macros,markup macros>> described below is
395 <<markup-macros,markup macros>> described below is preferred when linking to
538 This technique cannot be used with the <<markup-macros, markup macros>> that
545 [[markup-macros]]
548 This section discusses Asciidoc macros used in the document.
549 In addition to the macros defined by asciidoctor itself, additional macros
554 [[markup-macros-api]]
557 These macros must be used to tag command, structure, enumeration, enumerant,
561 The validation scripts (`make allchecks` output) also rely on these macros
563 The API markup macros, with examples of their use, are in the following
[all …]
/device/generic/vulkan-cereal/third-party/angle/src/libANGLE/renderer/d3d/
DHLSLCompiler.cpp230 const D3D_SHADER_MACRO *macros = overrideMacros ? overrideMacros : nullptr; in compileToBinary() local
241 result = mD3DCompileFunc(hlsl.c_str(), hlsl.length(), gl::g_fakepath, macros, nullptr, in compileToBinary()
258 if (macros != nullptr) in compileToBinary()
289 macros = nullptr; in compileToBinary()
317 if (macros == nullptr) in compileToBinary()
323 for (const D3D_SHADER_MACRO *mIt = macros; mIt->Name != nullptr; ++mIt) in compileToBinary()
/device/google/contexthub/firmware/os/drivers/st_lps22hb/
DREADME14 The driver requires that following macros are defined in the variant.h
25 * Define platform/variant dependent LPS22HB device macros
32 If these macros are not defined in the current variant the driver forces a compilation
/device/google/contexthub/firmware/os/drivers/st_hts221/
DREADME15 The driver requires that following macros are defined in the variant.h
25 * Define platform/variant dependent HTS221 device macros
33 If these macros are not defined in the current variant the driver forces a compilation
/device/generic/vulkan-cereal/protocols/vulkan/
Dstyleguide.txt110 However, because of the use of custom Ruby macros in the Vulkan
217 <<markup-macros-api, API Markup Macros>> section to match current
238 * 2020-04-29 - Expand use of `basetype` macros to include external API
242 section and document the apiext{cl} and reflink{cl} macros in the
243 <<markup-macros-api, API Markup Macros>> section.
259 macros.
260 * 2019-12-15 - Add a markup section on <<markup-macros-prime-symbols, Prime
266 <<markup-macros-api, API Markup Macros>> section (internal issue 1765).
328 <<markup-macros-api-name, *name{cl}>> and <<markup-macros-api-text,
329 *text{cl}>> markup macros instead of the *link{cl} macros, and clarify
[all …]
DBUILD.adoc236 If you are just testing Asciidoctor formatting, macros, stylesheets, etc.,
264 [[macros]] anchor in .Note
267 We use many custom Ruby macros in the reference pages and API spec
269 The validator scripts rely on these macros as part of their sanity checks,
270 and you should use the macros whenever referring to an API command, struct,
274 The supported macros are defined in the `config/spec-macros/extension.rb`
289 Most of these macros deeply need more intuitive names.
339 and Conventions`") document for details of our asciidoctor macros,
452 macros and DBLATEXPREFIX variable.
458 * 2015-09-02 - Initial version documenting macros, required toolchain
DrefPageNotes.md50 using the wrong macros, but are OK in the single-page apispec.html.
56 general, most of the ?name: macros can and should turn into ?link:,
58 * Need to tweak asciidoc macros for man pages (manpages.conf).
/device/google/contexthub/firmware/os/drivers/intersil_isl29034/
DREADME14 The driver requires that following macros are defined in the variant.h
20 If these macros are not defined in the current variant the driver forces a
35 * Define platform/variant dependent ISL29034 device macros
/device/generic/vulkan-cereal/third-party/googletest/googletest/include/gtest/internal/custom/
DREADME.md7 ### The following macros can be defined:
16 The following macros can be defined:
18 ### Flag related macros:
/device/google/contexthub/firmware/os/drivers/st_acc44/
DREADME17 The driver requires that following macros are defined in the variant.h
35 * Define platform/variant dependent ST_ACC44 device macros
53 If these macros are not defined in the current variant the driver forces a compilation
/device/google/contexthub/firmware/os/drivers/st_mag40/
DREADME18 The driver requires that following macros are defined in the variant.h
44 * Define platform/variant dependent ST_MAG40 device macros
58 If these macros are not defined in the current variant the driver forces a compilation
/device/generic/vulkan-cereal/protocols/vulkan/appendices/
Dboilerplate.txt40 * <<boilerplate-platform-macros,`vk_platform.h`>>, defining
41 platform-specific macros and headers.
48 In addition, specific preprocessor macros defined at the time
54 [[boilerplate-platform-macros]]
57 Platform-specific macros and interfaces are defined in `vk_platform.h`.
58 These macros are used to control platform-dependent behavior, and their
66 On many platforms the following macros are empty strings, causing platform-
93 With these macros, a Vulkan function declaration takes the form of:
140 of C preprocessor macros that are described below.
287 #defining macros before including `{full_header}`.
[all …]
/device/generic/vulkan-cereal/third-party/angle/tools/flex-bison/third_party/m4sugar/
Dm4sugar.m436 # long macros we define.
150 # must only be used on one argument at a time, and only on macros
164 # must only be used on macros known to be defined. Make sure this
171 # it must only be used on macros known to be defined. Make sure this
302 # difference is that `m4_ifset' is specialized on macros.
304 # In case of arguments of macros, eg. $1, it makes little difference.
452 # macros are generally used with list arguments, with quoting removed
562 # Some macros simply can't be renamed with this method: namely, anything
633 # replacement: if any of the defined macros contain unbalanced quoting, but
636 # handy, if you really need unbalanced quotes inside your macros.
[all …]
DREADME.chromium1 Name: Autoconf M4 macros used by Bison
10 Bison uses M4 to generate its output, and uses the utility M4 macros in this
Dforeach.m446 # On the other hand, in any version of M4, expanding additional macros
48 # fewer macros, these replacements actually pessimize performance.
61 # Form the common basis of the m4_foreach and m4_map macros. For each
214 # useful for making your macros more structured and readable by dropping
215 # unnecessary dnl's and have the macros indented properly.
/device/generic/vulkan-cereal/third-party/googletest/googlemock/include/gmock/internal/custom/
DREADME.md7 The following macros can be defined:
9 ### Flag related macros:
/device/generic/vulkan-cereal/third-party/angle/src/common/third_party/base/
DREADME.angle19 base/), and update the header guards and macros.
27 - header guards and macros are changed from BASE to ANGLEBASE to prevent conflicts.
/device/generic/vulkan-cereal/protocols/vulkan/katex/contrib/
Dauto-render.mjs208 … optionsCopy.errorCallback || console.error; // Enable sharing of global macros defined via `\gdef…
211 optionsCopy.macros = optionsCopy.macros || {};
Dauto-render.min.js1 ….ignoredClasses||[],r.errorCallback=r.errorCallback||console.error,r.macros=r.macros||{},function …
Dauto-render.js331 optionsCopy.macros = optionsCopy.macros || {};
/device/generic/vulkan-cereal/third-party/googletest/googletest/
DREADME.md138 you can easily tweak GoogleTest by defining control macros on the compiler
139 command line. Generally, these macros are named like `GTEST_XYZ` and you define
142 We list the most frequently used macros below. For a complete list, see file
195 In C++, macros don't obey namespaces. Therefore two libraries that both define a
/device/google/contexthub/firmware/os/drivers/st_lsm6dsm/
DREADME21 In order to build the driver for a platform some macros (see Macros list) must
23 Those macros define specific configuration that is platform dependent (SPI bus,
/device/generic/vulkan-cereal/third-party/googletest/googletest/cmake/
Dinternal_utils.cmake1 # Defines functions and macros useful for building Google Test and
9 # the functions and macros.
11 # - The functions/macros defined in this file may depend on Google
107 # Sun Pro doesn't provide macros to indicate whether exceptions and

123