[llvm-branch-commits] [llvm] IR: Introduce "float-abi" module flag (PR #210821)

Matt Arsenault via llvm-branch-commits llvm-branch-commits at lists.llvm.org
Tue Jul 21 00:18:06 PDT 2026


arsenm wrote:

> Why do we need a separate float-abi, rather than making it a part of target-abi?

I don't know, but these already coexist as distinct controls / concepts. e.g, test/CodeGen/ARM/tail-call-float.ll uses both `-target-abi aapcs -float-abi soft` and `-target-abi aapcs -float-abi hard` so they appear orthogonal. There would need to be a combinatorial explosion of ABI-name x float ABI to pack them into one string.

But as someone who does not care about either of these things, target-abi seems terrible. It's an opaque target specific string you have to parse to infer the piece of information you really want.

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


More information about the llvm-branch-commits mailing list