Displaying 3 results from an estimated 3 matches for "eightword".
Did you mean:
eightfold
2012 May 02
1
[LLVMdev] structs get decomposed when shouldn't
.../abi.pdf.
The complex rule 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,...
2012 May 02
0
[LLVMdev] structs get decomposed when shouldn't
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
2012 May 02
2
[LLVMdev] structs get decomposed when shouldn't
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