mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-22 18:54:02 +01:00
7ed143a4a1
Printing floating point number in decimal is inconvenient for humans. Verbose asm output will print out floating point values in comments, it helps. But in lots of cases, users still need additional work to covert the decimal back to hex or binary to check the bit patterns, especially when there are small precision difference. Hexadecimal form is one of the supported form in LLVM IR, and easier for debugging. This patch try to print all FP constant in hex form instead. Reviewed By: RKSimon Differential Revision: https://reviews.llvm.org/D73566
35 lines
1.0 KiB
LLVM
35 lines
1.0 KiB
LLVM
; RUN: llc -verify-machineinstrs -mtriple=powerpc64-none-linux < %s | FileCheck %s
|
|
|
|
; Check that all current floating-point types are correctly emitted to assembly
|
|
; on a big-endian target. x86_fp80 can't actually print for unrelated reasons,
|
|
; but that's not really a problem.
|
|
|
|
@var128 = global fp128 0xL00000000000000008000000000000000, align 16
|
|
@varppc128 = global ppc_fp128 0xM80000000000000000000000000000000, align 16
|
|
@var64 = global double -0.0, align 8
|
|
@var32 = global float -0.0, align 4
|
|
@var16 = global half -0.0, align 2
|
|
|
|
; CHECK: var128:
|
|
; CHECK-NEXT: .quad 0x8000000000000000 # fp128 -0
|
|
; CHECK-NEXT: .quad 0
|
|
; CHECK-NEXT: .size
|
|
|
|
; CHECK: varppc128:
|
|
; CHECK-NEXT: .quad 0x8000000000000000 # ppc_fp128 -0
|
|
; CHECK-NEXT: .quad 0
|
|
; CHECK-NEXT: .size
|
|
|
|
; CHECK: var64:
|
|
; CHECK-NEXT: .quad 0x8000000000000000 # double -0
|
|
; CHECK-NEXT: .size
|
|
|
|
; CHECK: var32:
|
|
; CHECK-NEXT: .long 0x80000000 # float -0
|
|
; CHECK-NEXT: .size
|
|
|
|
; CHECK: var16:
|
|
; CHECK-NEXT: .short 0x8000 # half -0
|
|
; CHECK-NEXT: .size
|
|
|