# Cholesky promotes Float16

**URL:** https://discourse.julialang.org/t/cholesky-promotes-float16/76772
**Category:** Numerics
**Tags:** question
**Created:** [February 19, 2022, 7:07pm UTC](https://discourse.julialang.org/t/cholesky-promotes-float16/76772 "2022-02-19T19:07:07Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![gbaraldi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gbaraldi/32/22101_2.png) [@gbaraldi](https://discourse.julialang.org/u/gbaraldi)
#### Post date: [February 20, 2022, 1:47am UTC](https://discourse.julialang.org/t/cholesky-promotes-float16/76772/6 "2022-02-20T01:47:57Z")

</div>

I think there are two issues at play. First thing is that the LAPACK implementation that julia uses doesn’t have float16 routines which is probably why it has to get promoted, the other is that julia currently has a compiler pass to promote Float16 computations to Float32.  
One thing that could be done is to truncate the result after doing the LAPACK routine so the user gets a Float16 back.  
I think in a previous thread you opened I gave more details [Half precision](https://discourse.julialang.org/t/half-precision/75580)

---

_[View the full topic](https://discourse.julialang.org/t/cholesky-promotes-float16/76772)._