search for: sseup

...le appears to be reversion to stack if not all of an aggregate would fit in registers. Couldn't this be implemented rather easily if LLVM *did* take note of structs as a whole? Clang would pass pass its aggregate as an LLVM struct with each field being an appropriate eightword (or larger if SSEUP fields were involved). LLVM would decide whether enough registers are free for the whole thing and either use them or shove it on the stack. Though, having just seen the X86_64 implementation in clang, it's nowhere near as horrific as I'd feared it would be. In fact, it's probably si...

Hi Tim, On 02/05/12 10:51, Tim Northover wrote: > On Wednesday 02 May 2012 09:12:16 Duncan Sands wrote: >>> As I can understand, LLVM is trying to decompose datatypes into smaller >>> components in some circumstances. >> >> Can you please explain more what you are referring to here. LLVM itself >> shouldn't be changing function parameters or return

> 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

On Wednesday 02 May 2012 09:12:16 Duncan Sands wrote: > > As I can understand, LLVM is trying to decompose datatypes into smaller > > components in some circumstances. > > Can you please explain more what you are referring to here. LLVM itself > shouldn't be changing function parameters or return types unless the > function has local (internal) linkage (since in that

...it *explicitly-ABI-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,...