bb0bbed610
This makes the bytecode reader/writer work on big-endian platforms. The only problem was related to encoding of multi-byte integers, where both reader and writer code make implicit assumptions about endianness of the host platform. This fixes the current test failures on s390x, and in addition allows to remove the UNSUPPORTED markers from all other bytecode-related test cases - they now also all pass on s390x. Also adding a GFAIL_SKIP to the MultiModuleWithResource unit test, as this still fails due to an unrelated endian bug regarding decoding of external resources. Differential Revision: https://reviews.llvm.org/D153567 Reviewed By: mehdi_amini, jpienaar, rriddle
23 lines
1.1 KiB
MLIR
23 lines
1.1 KiB
MLIR
// This file contains test cases related to roundtripping.
|
|
|
|
//===--------------------------------------------------------------------===//
|
|
// Test roundtrip
|
|
//===--------------------------------------------------------------------===//
|
|
|
|
// RUN: mlir-opt %S/versioned-op-1.12.mlirbc -emit-bytecode \
|
|
// RUN: -emit-bytecode-version=0 | mlir-opt -o %t.1 && \
|
|
// RUN: mlir-opt %S/versioned-op-1.12.mlirbc -o %t.2 && \
|
|
// RUN: diff %t.1 %t.2
|
|
|
|
//===--------------------------------------------------------------------===//
|
|
// Test invalid versions
|
|
//===--------------------------------------------------------------------===//
|
|
|
|
// RUN: not mlir-opt %S/versioned-op-1.12.mlirbc -emit-bytecode \
|
|
// RUN: -emit-bytecode-version=-1 2>&1 | FileCheck %s --check-prefix=ERR_VERSION_NEGATIVE
|
|
// ERR_VERSION_NEGATIVE: unsupported version requested -1, must be in range [{{[0-9]+}}, {{[0-9]+}}]
|
|
|
|
// RUN: not mlir-opt %S/versioned-op-1.12.mlirbc -emit-bytecode \
|
|
// RUN: -emit-bytecode-version=999 2>&1 | FileCheck %s --check-prefix=ERR_VERSION_FUTURE
|
|
// ERR_VERSION_FUTURE: unsupported version requested 999, must be in range [{{[0-9]+}}, {{[0-9]+}}]
|