freaknbigpanda wrote: > Anyways if we want to implement the following semantics (which match GCC): > > * call site ABI is determined based on caller target attributes > * the callee’s target attributes affects how the callee itself is compiled > * Do not force callers with a lower target attribute AVX level to change > their calling convention, but emit warnings > > Then I think we can't encode the AVX level into the function type since we > would be ignoring the AVX level in the function type at call sites. What do > you think?
Hey @efriedma-quic I have implemented the semantics above, can you take another pass on the PR and let me know what you think? @vortex73 I saw that you merged in https://github.com/llvm/llvm-project/pull/194460 recently. Can you see any issues with the work you are doing with LLVMABI and the direction that this PR is going in? Just want to make sure that per function AVX level is respected going forward. https://github.com/llvm/llvm-project/pull/193298 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
