# Ensure release_base is set on linux
build:release_linux_base --config=release_base

# Disable clang extension that rejects type definitions within offsetof.
# This was added in clang-16 by https://reviews.llvm.org/D133574.
# Can be removed once upb is updated, since a type definition is used within
# offset of in the current version of ubp.

    /**
     * Logger for this class.
     */
    protected static final Logger logger = LogManager.getLogger(AbstractXmlExtractor.class);

    /**
     * UTF-7 Byte Order Mark definition.
     */
    protected static final ByteOrderMark BOM_UTF_7 = new ByteOrderMark("UTF-7", 0x2B, 0x2F, 0x76);

    /**
     * HTML4 unescape translator.
     */

                    }
                }
            }

            if (destroyer != null) {
                destroyer.accept(instance);
            }
        }
    }

    /**
     * A definition for a component that can be instantiated on demand.
     * This class handles component creation, dependency injection, and initialization.
     *
     * @param <T> the type of the component
     */

</p>

<h2 id="model">Memory Model</h2>

<p>
The following formal definition of Go's memory model closely follows
the approach presented by Hans-J. Boehm and Sarita V. Adve in
“<a href="https://dl.acm.org/doi/10.1145/1375581.1375591">Foundations of the C++ Concurrency Memory Model</a>”,
published in PLDI 2008.
The definition of data-race-free programs and the guarantee of sequential consistency

        deprecated in TF 2.2.

*   `tf.lite`:

    *   `tf.quantization.quantize_and_dequantize_v2` has been introduced, which
        updates the gradient definition for quantization which is outside the
        range to be 0. To simulate the V1 the behavior of
        `tf.quantization.quantize_and_dequantize(...)` use

# don't pass --nobuild, so they're on their own.
#
# Although buildifier checks for formatting as well, "bazel build nobuild"
# checks for cross-file issues like bad includes or missing BUILD definitions.
#
# We can't test on the windows toolchains because they're using a legacy
# toolchain format (or something) that specifies the toolchain directly instead