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
27 lines
1.3 KiB
MLIR
27 lines
1.3 KiB
MLIR
// This file contains various failure test cases related to the structure of
|
|
// the string section.
|
|
|
|
//===--------------------------------------------------------------------===//
|
|
// Count
|
|
//===--------------------------------------------------------------------===//
|
|
|
|
// RUN: not mlir-opt %S/invalid-string_section-count.mlirbc 2>&1 | FileCheck %s --check-prefix=COUNT
|
|
// COUNT: attempting to parse a byte at the end of the bytecode
|
|
|
|
//===--------------------------------------------------------------------===//
|
|
// Invalid String
|
|
//===--------------------------------------------------------------------===//
|
|
|
|
// RUN: not mlir-opt %S/invalid-string_section-no_string.mlirbc 2>&1 | FileCheck %s --check-prefix=NO_STRING
|
|
// NO_STRING: attempting to parse a byte at the end of the bytecode
|
|
|
|
// RUN: not mlir-opt %S/invalid-string_section-large_string.mlirbc 2>&1 | FileCheck %s --check-prefix=LARGE_STRING
|
|
// LARGE_STRING: string size exceeds the available data size
|
|
|
|
//===--------------------------------------------------------------------===//
|
|
// Trailing data
|
|
//===--------------------------------------------------------------------===//
|
|
|
|
// RUN: not mlir-opt %S/invalid-string_section-trailing_data.mlirbc 2>&1 | FileCheck %s --check-prefix=TRAILING_DATA
|
|
// TRAILING_DATA: unexpected trailing data between the offsets for strings and their data
|