// RUN: stablehlo-quant-opt %s -stablehlo-merge-fusion-with-dequantize -split-input-file -verify-diagnostics | FileCheck %s

// Merge fusion with dequantize for relu case.

module attributes {tf_saved_model.semantics} {
  // CHECK-LABEL: func.func private @merge_relu_fusion
  func.func private @merge_relu_fusion(%arg0: tensor<1x4xf32>) -> tensor<1x3xf32> {

apiVersion: release-notes/v2
kind: bug-fix
area: traffic-management
issues:
- 40474
releaseNotes:
- |
  **Fixed** an issue causing traffic to not match (and return a `404`) when using wildcard domain names and including an unexpected port in the `Host` header.
- |
  **Fixed** an issue causing traffic to match an unexpected route when using wildcard domain names and including an port in the `Host` header.
- |

// ops in the function.
void ConvertMlirQuantOpsToTFLQuantOps(func::FuncOp func);

// A helper class to convert target function to another representation using
// `ConvertForward` function during construction and convert target function
// back to the original representation using `ConvertBackward` function during
// deconstruction.
template <void (*ConvertForward)(func::FuncOp),
          void (*ConvertBackward)(func::FuncOp)>
class ScopedOpsConverter {

 * <p>
 * Any other type of response will be treated as an error, causing the remote cache to be disabled for the remainder of the build.
 * <p>
 * When credentials are configured (see {@link #getCredentials()}), they are sent using HTTP Basic Auth.
 * <p>
 * Requests that fail during request transmission, after having established a TCP connection, will automatically be retried.

 *     <li>A {@link Named} type created using {@link org.gradle.api.model.ObjectFactory#named(Class, String)}.</li>
 *     <li>Any serializable type.</li>
 * </ul>
 *
 * @since 4.0
 */
public interface ActionConfiguration {
    /**
     * Adds initialization parameters to use when constructing an instance of the implementation class.
     *
     * @param params - the parameters to use during construction
     */

Any direct modification or reading of another project's object creates coupling between the projects.
Coupling during configuration can result in flawed build outcomes when using 'configuration on demand', while coupling during execution can affect parallel execution.

One common source of coupling is configuration injection, such as using `allprojects{}` or `subprojects{}` in build scripts.

To avoid coupling issues, it's recommended to:

     * Determines whether a builder for the {@link org.gradle.tooling.model.GradleProject} model should realize tasks.
     * <p>
     * This method has to be invoked during builder execution time to provide an effective value.
     * That is due to Android Studio (via Intellij IDEA) using {@code LongRunningOperation.withArguments()} to configure the value of the option.
     */
    public static boolean shouldRealizeTasks() {

// instruction in the wrapper methods generated for T1.M and (*T1).M,
// causing a spurious "live at entry: ~r1" for the return result.

type T struct {
}

func (t *T) M() *int

type T1 struct {
	*T
}

// Liveness analysis used to have the VARDEFs in the wrong place,
// causing a temporary to appear live on entry.

func f1(pkg, typ, meth string) {

  - Variant 'api' declares a component, as well as attribute 'custom' with value 'c1':
      - Incompatible because this component declares a component for use during compile-time and the consumer needed a component for use during runtime
  - Variant 'runtime' declares a component for use during runtime:

# Test with coverage instrumentation enabled (-fuzz) and race instrumentation
# but without actually fuzzing the target (by using a non-matching pattern)
go test -fuzz=xxx -race -v
! stderr 'race detected during execution of test'

# Test with just race instrumentation enabled
go test -race -v
! stderr 'race detected during execution of test'

# Test with coverage and race instrumentation enabled, and a matching fuzz
# pattern