llvm-mirror/test/CodeGen/X86/constant-pool-remat-0.ll

; REQUIRES: asserts
; RUN: llc < %s -mtriple=x86_64-linux   | FileCheck %s
; RUN: llc < %s -mtriple=x86_64-linux -regalloc=greedy | FileCheck %s
; RUN: llc < %s -march=x86 -mattr=+sse2 | FileCheck %s
; CHECK:     LCPI
; CHECK:     LCPI
; CHECK:     LCPI
; CHECK-NOT: LCPI

; RUN: llc < %s -mtriple=x86_64-linux -o /dev/null -stats -info-output-file - | FileCheck %s -check-prefix=X64stat
; X64stat: 6 asm-printer

; RUN: llc < %s -march=x86 -mattr=+sse2 -o /dev/null -stats -info-output-file - | FileCheck %s -check-prefix=X32stat
; X32stat: 12 asm-printer

declare float @qux(float %y)

define float @array(float %a) nounwind {
  %n = fmul float %a, 9.0
  %m = call float @qux(float %n)
  %o = fmul float %m, 9.0
  ret float %o
}
Revert the test moves from 176733. Use "REQUIRES: asserts" instead. llvm-svn: 176873 2013-03-12 17:27:52 +01:00			`; REQUIRES: asserts`
test/CodeGen/X86/constant-pool-remat-0.ll: FileCheck-ize and add explicit -mtriple=x86_64-linux. llvm-svn: 127775 2011-03-17 00:01:31 +01:00			`; RUN: llc < %s -mtriple=x86_64-linux \| FileCheck %s`
When dead code elimination removes all but one use, try to fold the single def into the remaining use. Rematerialization can leave single-use loads behind that we might as well fold whenever possible. llvm-svn: 128918 2011-04-05 22:20:26 +02:00			`; RUN: llc < %s -mtriple=x86_64-linux -regalloc=greedy \| FileCheck %s`
test/CodeGen/X86/constant-pool-remat-0.ll: FileCheck-ize and add explicit -mtriple=x86_64-linux. llvm-svn: 127775 2011-03-17 00:01:31 +01:00			`; RUN: llc < %s -march=x86 -mattr=+sse2 \| FileCheck %s`
			`; CHECK: LCPI`
			`; CHECK: LCPI`
			`; CHECK: LCPI`
			`; CHECK-NOT: LCPI`

			`; RUN: llc < %s -mtriple=x86_64-linux -o /dev/null -stats -info-output-file - \| FileCheck %s -check-prefix=X64stat`
			`; X64stat: 6 asm-printer`

			`; RUN: llc < %s -march=x86 -mattr=+sse2 -o /dev/null -stats -info-output-file - \| FileCheck %s -check-prefix=X32stat`
			`; X32stat: 12 asm-printer`
Mark the SSE and MMX load instructions that X86InstrInfo::isReallyTriviallyReMaterializable knows how to handle with the isReMaterializable flag so that it is given a chance to handle them. Without hoisting constant-pool loads from loops this isn't very visible, though it does keep CodeGen/X86/constant-pool-remat-0.ll from making a copy of the constant pool on the stack. llvm-svn: 40736 2007-08-02 16:27:55 +02:00
If SSE2 is available, x86 should pass first 3 f32/f64 arguments in XMM registers for fastcc calls. llvm-svn: 55840 2008-09-05 19:24:07 +02:00			`declare float @qux(float %y)`
Mark the SSE and MMX load instructions that X86InstrInfo::isReallyTriviallyReMaterializable knows how to handle with the isReMaterializable flag so that it is given a chance to handle them. Without hoisting constant-pool loads from loops this isn't very visible, though it does keep CodeGen/X86/constant-pool-remat-0.ll from making a copy of the constant pool on the stack. llvm-svn: 40736 2007-08-02 16:27:55 +02:00
If SSE2 is available, x86 should pass first 3 f32/f64 arguments in XMM registers for fastcc calls. llvm-svn: 55840 2008-09-05 19:24:07 +02:00			`define float @array(float %a) nounwind {`
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 llvm-svn: 72897 2009-06-05 00:49:04 +02:00			`%n = fmul float %a, 9.0`
If SSE2 is available, x86 should pass first 3 f32/f64 arguments in XMM registers for fastcc calls. llvm-svn: 55840 2008-09-05 19:24:07 +02:00			`%m = call float @qux(float %n)`
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 llvm-svn: 72897 2009-06-05 00:49:04 +02:00			`%o = fmul float %m, 9.0`
Mark the SSE and MMX load instructions that X86InstrInfo::isReallyTriviallyReMaterializable knows how to handle with the isReMaterializable flag so that it is given a chance to handle them. Without hoisting constant-pool loads from loops this isn't very visible, though it does keep CodeGen/X86/constant-pool-remat-0.ll from making a copy of the constant pool on the stack. llvm-svn: 40736 2007-08-02 16:27:55 +02:00			`ret float %o`
			`}`