Displaying 2 results from an estimated 2 matches for "reg3b".
Did you mean:
reg32
2014 Jun 08
2
[LLVMdev] [llvm] r210424 - Revert "Do materialize for floating point"
...ouble 1.234567e+00, double* @de, align 8
> -; CHECK: .ent d1
> -; CHECK: lui $[[REG1a:[0-9]+]], 16371
> -; CHECK: ori $[[REG2a:[0-9]+]], $[[REG1a]], 49353
> -; CHECK: lui $[[REG1b:[0-9]+]], 21403
> -; CHECK: ori $[[REG2b:[0-9]+]], $[[REG1b]], 34951
> -; CHECK: mtc1 $[[REG2b]], $f[[REG3b:[0-9]+]]
> -; CHECK: mtc1 $[[REG2a]], $f[[REG3a:[0-9]+]]
> -; CHECK: sdc1 $f[[REG3b]], 0(${{[0-9]+}})
> -; CHECK: .end d1
> - ret void
> -}
> -
> -attributes #0 = { nounwind "less-precise-fpmad"="false" "no-frame-pointer-elim"="true" &qu...
2017 Feb 14
2
Ensuring chain dependencies with expansion to libcalls
Hi all,
Our target does not have native support for 64-bit integers, so we rely on
library calls for certain operations (like sdiv). We recently ran into a
problem where these operations that are expanded to library calls aren't
maintaining the proper ordering in relation to other chains in the DAG.
The following snippet of a DAG demonstrates the problem.
t0: ch = EntryToken
t2: