llvm-mirror/test/Bitcode/invalid-functionptr-align.ll

; Bitcode with invalid function pointer alignment.

; RUN: not --crash llvm-dis %s.bc -o - 2>&1 | FileCheck %s

CHECK: LLVM ERROR: Alignment is neither 0 nor a power of 2
[DataLayout] Check StackNatural and FunctionPtr alignments. MaybeAlignment asserts that the passed in value is == 0 or a power of 2. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16272 Reviewers: michaelplatings, gchatelet, jakehehrlich, jfb Reviewed By: gchatelet Tags: #llvm Differential Revision: https://reviews.llvm.org/D65858 llvm-svn: 368191 2019-08-07 19:20:55 +02:00			`; Bitcode with invalid function pointer alignment.`

Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`""" This reverts commit 80a34ae31125aa46dcad47162ba45b152aed968d with fixes. Previously, since bots turning on EXPENSIVE_CHECKS are essentially turning on MachineVerifierPass by default on X86 and the fact that inline-asm-avx-v-constraint-32bit.ll and inline-asm-avx512vl-v-constraint-32bit.ll are not expected to generate functioning machine code, this would go down to `report_fatal_error` in MachineVerifierPass. Here passing `-verify-machineinstrs=0` to make the intent explicit. 2020-02-12 08:01:35 +01:00			`; RUN: not --crash llvm-dis %s.bc -o - 2>&1 \| FileCheck %s`
[DataLayout] Check StackNatural and FunctionPtr alignments. MaybeAlignment asserts that the passed in value is == 0 or a power of 2. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16272 Reviewers: michaelplatings, gchatelet, jakehehrlich, jfb Reviewed By: gchatelet Tags: #llvm Differential Revision: https://reviews.llvm.org/D65858 llvm-svn: 368191 2019-08-07 19:20:55 +02:00
			`CHECK: LLVM ERROR: Alignment is neither 0 nor a power of 2`