https://github.com/andykaylor commented:
I'm concerned that this is a more general problem. Any runtime function call we create after calling convention lowering is going to be vulnerable to this class of problem. Is there a way that we could add some kind of handling to build a runtime function and a function call in a way that consulted the ABI library to get the calling convention details right? Beyond that, the existing handling for the complex division promote case is wrong. It should really be determining that promotion type (if available) during codegen and attaching that to the operation as an attribute. @AmrDeveloper is this something you could handle? https://github.com/llvm/llvm-project/pull/216498 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
