llvm/test/MC/ELF/bracket-exprs.s

// RUN: llvm-mc -triple i386-unknown-unknown %s | FileCheck %s

// CHECK: .byte 1
.if [~0 >> 63] == 1
.byte 1
.else
.byte 2
.endif

// CHECK: .byte 3
.if 4 * [4 + (3 + [2 * 2] + 1)] == 48
.byte 3
.else
.byte 4
.endif
Restore r125595 (reverted in r126336) with modifications: Introduce a variable in the AsmParserExtension whether [] is valid in an expression. If it is true, parse them like (). Enable this for ELF only. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@126443 91177308-0d34-0410-b5e6-96231b3b80d8 2011-02-24 21:59:22 +00:00			`// RUN: llvm-mc -triple i386-unknown-unknown %s \| FileCheck %s`

			`// CHECK: .byte 1`
[MC] Use LShr for constant evaluation of ">>" on ELF/arm64--darwin. This matches other assemblers and is less unexpected (e.g. PR23227). On ELF, I tried binutils gas v2.24 and nasm 2.10.09, and they both agree on LShr. On COFF, I couldn't get my hands on an assembler yet, so don't change the behavior. For now, don't change it on non-AArch64 Darwin either, as the other assembler is gas v1.38, which does an AShr. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@235963 91177308-0d34-0410-b5e6-96231b3b80d8 2015-04-28 01:37:11 +00:00			`.if [~0 >> 63] == 1`
Restore r125595 (reverted in r126336) with modifications: Introduce a variable in the AsmParserExtension whether [] is valid in an expression. If it is true, parse them like (). Enable this for ELF only. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@126443 91177308-0d34-0410-b5e6-96231b3b80d8 2011-02-24 21:59:22 +00:00			`.byte 1`
			`.else`
			`.byte 2`
			`.endif`

			`// CHECK: .byte 3`
			`.if 4 * [4 + (3 + [2 * 2] + 1)] == 48`
			`.byte 3`
			`.else`
			`.byte 4`
			`.endif`