[Mlir-commits] [mlir] [MLIR] Add f8E8M0FNU type (PR #111028)

[Diego Caballero]

dcaballe wrote:

Yeah, we’re definitely dealing with a combinatorial explosion. For the compiler internals, have we thought about using a single FP type that models different E/M sizes and supports the required feature flags for the specific semantics of these formats? I wonder, though, if we need verification at some level (bindings?) to ensure compliance with the micro-scaling standard... Or do we want to leave the door open to arbitrary format? I'm not sure I fully understand the implications of the latter.

> but at what point, upon removing all features that traditionally make something a "floating point number" 

I would say they are still floating-point in spirit :). I’m not sure we could treat them differently. There are specific FP semantics that still apply to these formats, such as NaN propagation (e.g., minnum/maxnum/minimum/maximum), exceptions, overflow...

https://github.com/llvm/llvm-project/pull/111028