On Thu Oct 8, 2026 at 11:24 PM CDT, Andrea Pinski wrote: > On Thu, Oct 8, 2026 at 9:13 PM Trevor Gross <[email protected]> wrote: >> >> On Thu Oct 8, 2026 at 10:41 PM CDT, Andrea Pinski wrote: >> >> I expected this to be the first reply :) Indeed many C implementations >> will probably not care to implement _Float16 everywhere, if at all. >> >> As I think you mentioned in the followup, I'm mostly working on this for >> rust support (thought depending on the solution, other LLVM-based >> languages might get some benefit). We're not planning for it to be >> optional because we are able to support f16 on every target with the >> sole exception of i586-*, and special casing would be a user annoyance >> (though minor). So tradeoff between my headache now figuring out >> something reasonable, vs. kicking the can to all future users to config >> it out. Regrettably I think the first is worth it. >> >> Why is anybody building for pentium still? I have no idea, but a number >> of distros use it as their baseline. GCC is probably comfortable saying >> they don't want to support _Float16 in this case, but that's why I'm >> approaching this from a coordination perspective rather than as a >> feature request. > > > If you want to make this a rust only feature then you don't need any > coordination at all. Name the routines from the rust front-end > themselves and implement it in the rust support library. > Problem solved.
That is more or less what it would be anyway, though ideally with some backend support for the optimizations. And I think there was some Julia interest. But yeah, I wasn't expecting a whole lot here outside of possible naming concerns or something else I missed. - Trevor
