| /openbmc/intel-ipmi-oem/include/ |
| H A D | biosxml.hpp | 378 std::stack<knob::DepexOperators>& operators, in evaluateExprStack() argument
381 if (values.size() != (operators.size() + 1)) in evaluateExprStack()
386 while (!operators.empty()) in evaluateExprStack()
394 switch (operators.top()) in evaluateExprStack()
476 operators.pop(); in evaluateExprStack()
507 std::stack<knob::DepexOperators> operators; in evaluateExpression() local
533 if (!operators.empty()) in evaluateExpression()
535 if (!evaluateExprStack(values, operators, value)) in evaluateExpression()
543 operators.emplace(knob::DepexOperators::OR); in evaluateExpression()
551 if (!operators.empty()) in evaluateExpression()
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.commands.itest | 4 Now table driven to allow the operators
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/octave/ |
| H A D | octave_7.2.0.bb | 47 for folder in "liboctave/operators liboctave/numeric liboctave/array liboctave/util"; do
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-4.0.rst | 196 :append/:prepend in combination with other operators
199 The ``append``, ``prepend`` and ``remove`` operators can now only be combined with
200 ``=`` and ``:=`` operators. To the exception of the ``append`` plus ``+=`` and
203 confusion on how the override style syntax operators work and should be used.
208 the same behavior. You can learn more about override style syntax operators
|
| H A D | release-notes-3.4.1.rst | 28 - bitbake: Revert "parse/ast: Show errors for append/prepend/remove operators combined with +=/.="
41 - bitbake: parse/ast: Show errors for append/prepend/remove operators combined with +=/.=
|
| H A D | migration-1.8.rst | 163 multiple licenses are specified with no operators to specify how the
|
| H A D | migration-3.4.rst | 240 you will need to use a mirror or address the issue with the operators
|
| /openbmc/qemu/target/hexagon/idef-parser/ |
| H A D | macros.h.inc | 117 /* Unary operators */
120 /* Binary operators */
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-metadata.rst | 11 describes the available syntax and operators as well as provides
200 assignment operators. The "??=" operator takes effect immediately, replacing
264 the "+=" and "=+" operators. These operators insert a space between the
267 These operators take immediate effect during parsing. Here are some
284 the ".=" and "=." operators.
286 These operators take immediate effect during parsing. Here are some
303 These operators differ from the ":=", ".=", "=.", "+=", and "=+"
304 operators in that their effects are applied at variable expansion time
385 ":remove" as compared to the "+=" and "=+" operators is that the
386 override style operators provide guaranteed operations. For example,
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/poco/poco/ |
| H A D | 0001-SimpleRowFormatter.h-fix-the-build-on-gcc-15-unsatis.patch | 29 assignment operators that involve rvalue references?
|
| /openbmc/docs/designs/ |
| H A D | redfish-pcie.md | 29 administrators and operators.
|
| H A D | redfish-spdm-attestation.md | 35 providing system administrators and operators an easy way to remotely verify the
|
| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 389 - Insert whitespace around binary operators for readability.
396 - Do not insert whitespace around unary operators.
417 - Prefer line-breaks after operators to show continuation.
|
| /openbmc/qemu/docs/devel/ |
| H A D | writing-monitor-commands.rst | 357 machines, as opposed to exclusively human operators.
360 for human operators. While they may return large amounts of formatted
544 useful only to human operators.
|
| /openbmc/qemu/docs/specs/ |
| H A D | vmgenid.rst | 88 * Disassembling to symbolic ASL+ operators
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | customizing-images.rst | 34 with operators like ``?=``. Using ``:append`` ensures the operation
|
| H A D | new-recipe.rst | 1409 practices, such as omitting spaces around ``=`` operators in assignments
1563 operators have been applied and after all ``=`` assignments have
1583 and ``=+`` operators have been applied and after all ``=``
|
| /openbmc/phosphor-debug-collector/ |
| H A D | .clang-tidy | 324 readability-operators-representation,
|
| /openbmc/dbus-sensors/ |
| H A D | .clang-tidy | 305 readability-operators-representation,
|
| /openbmc/openbmc/poky/meta/recipes-core/meta/ |
| H A D | cve-update-db-native.bb | 265 # Parse start version, end version and operators
|
| H A D | cve-update-nvd2-native.bb | 305 # Parse start version, end version and operators
|
| /openbmc/bmcweb/ |
| H A D | .clang-tidy | 325 readability-operators-representation,
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | yp-intro.rst | 723 BitBake also supports both ``:prepend`` and ``:append`` operators as a
724 method of extending task functionality. These operators inject code into
726 operators, see the
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 79 operator. You can learn more about these operators in the
|
| /openbmc/u-boot/test/py/ |
| H A D | README.md | 152 logical operators are supported. For example:
|