llvm-project/llvm/test/Assembler/2002-04-07-InfConstant.ll

; The output formater prints out 1.0e100 as Inf!
;
; RUN: llvm-as < %s | llvm-dis | llvm-as | llvm-dis | grep 0x7FF0000000000000

define float @test() {
        %tmp = fmul float 0x7FF0000000000000, 1.000000e+01               ; <float> [#uses=1]
        ret float %tmp
}
Testcase for bad constant handling llvm-svn: 2133 2002-04-07 15:58:25 +08:00			`; The output formater prints out 1.0e100 as Inf!`
			`;`
Make this test slightly more strict. llvm-svn: 70180 2009-04-27 11:05:26 +08:00			`; RUN: llvm-as < %s \| llvm-dis \| llvm-as \| llvm-dis \| grep 0x7FF0000000000000`
Testcase for bad constant handling llvm-svn: 2133 2002-04-07 15:58:25 +08:00
Remove llvm-upgrade llvm-svn: 47119 2008-02-14 15:57:12 +08:00			`define float @test() {`
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 06:49:04 +08:00			`%tmp = fmul float 0x7FF0000000000000, 1.000000e+01 ; <float> [#uses=1]`
Remove llvm-upgrade llvm-svn: 47119 2008-02-14 15:57:12 +08:00			`ret float %tmp`
			`}`
Testcase for bad constant handling llvm-svn: 2133 2002-04-07 15:58:25 +08:00