Displaying 2 results from an estimated 2 matches for "x87up".
Did you mean:
x87
2020 Jun 03
5
[cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
> On Jun 2, 2020, at 4:21 PM, comex via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>
> 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
2020 Jun 04
2
[cfe-dev] Clang/LLVM function ABI lowering (was: Re: [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM)
...I-specific* data (metadata?),
> reflecting the extra information that the ABI rules require the
> backend to
> know about the type. E.g., for X86_64, clang needs to inform LLVM of
> the
> classification for each parameter's type into MEMORY, INTEGER, SSE,
> SSEUP,
> X87, X87UP, COMPLEX_X87. Or, for PPC64 elfv2, Clang needs to inform
> LLVM
> when a structure should be treated as a "homogenous aggregate" of
> floating-point or vector type. (In both cases, that information cannot
> correctly be extracted from the LLVM IR struct type, only from the C...