[llvm-dev] [cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM (original) (raw)
David Greene via llvm-dev llvm-dev at lists.llvm.org
Wed Jun 3 08:41:20 PDT 2020
- Previous message: [llvm-dev] [cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
- Next message: [llvm-dev] [cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
comex via cfe-dev <cfe-dev at lists.llvm.org> writes:
While this is a different area of the codebase, another thing that would benefit greatly from being moved out of Clang is function call ABI handling. Currently, that handling is split awkwardly between Clang and LLVM proper, forcing frontends that implement C FFI to either recreate the Clang parts themselves (like Rust does), depend on Clang (like Swift does), or live with FFI just not working with some function signatures. I'm not sure what Flang currently does, but my understanding is that Flang does support C FFI, so it would probably benefit from this as well. Just something to consider. :)
Yep, C interop is part of the Fortran standard so flang will have to support it.
This has been talked about before but as yet nothing has happened with it. Maybe this is our opportunity.
-David- Previous message: [llvm-dev] [cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
- Next message: [llvm-dev] [cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]