llvm-6502/test/Transforms/GlobalOpt/2008-01-29-VolatileGlobal.ll

; RUN: llvm-as < %s | opt -globalopt | llvm-dis | grep {volatile load}
@t0.1441 = internal global double 0x3FD5555555555555, align 8		; <double*> [#uses=1]

define double @foo() nounwind  {
entry:
	%tmp1 = volatile load double* @t0.1441, align 8		; <double> [#uses=2]
	%tmp4 = fmul double %tmp1, %tmp1		; <double> [#uses=1]
	ret double %tmp4
}
Don't let globalopt hack on volatile loads or stores. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@46523 91177308-0d34-0410-b5e6-96231b3b80d8 2008-01-29 19:01:37 +00:00			`; RUN: llvm-as < %s \| opt -globalopt \| llvm-dis \| grep {volatile load}`
			`@t0.1441 = internal global double 0x3FD5555555555555, align 8 ; <double*> [#uses=1]`

			`define double @foo() nounwind {`
			`entry:`
			`%tmp1 = volatile load double* @t0.1441, align 8 ; <double> [#uses=2]`
Split the Add, Sub, and Mul instruction opcodes into separate integer and floating-point opcodes, introducing FAdd, FSub, and FMul. For now, the AsmParser, BitcodeReader, and IRBuilder all preserve backwards compatability, and the Core LLVM APIs preserve backwards compatibility for IR producers. Most front-ends won't need to change immediately. This implements the first step of the plan outlined here: http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@72897 91177308-0d34-0410-b5e6-96231b3b80d8 2009-06-04 22:49:04 +00:00			`%tmp4 = fmul double %tmp1, %tmp1 ; <double> [#uses=1]`
Don't let globalopt hack on volatile loads or stores. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@46523 91177308-0d34-0410-b5e6-96231b3b80d8 2008-01-29 19:01:37 +00:00			`ret double %tmp4`
			`}`