Displaying 2 results from an estimated 2 matches for "dn375768".
Did you mean:
375768
2013 Dec 24
2
[LLVMdev] [cfe-dev] [Proposal] function attribute to reduce emission of vzeroupper instructions
> In general, I'm not too keen on adding more calling conventions unless
> there's a really powerful need for one from an ABI perspective. This
> sounds more like an optimization than an ABI need.
I think that is the case.
> What's more, I
> worry (a little bit) about confusion that could be caused with the
> __vectorcall calling convention (which we do not
2016 Nov 30
2
RFC: Adding Support For Vectorcall Calling Convention
...vector/HVA types. The size is fixed to 8 bytes per argument.
- HVA types are returned in XMM0/YMM0/ZMM0 to XMM3/YMM3/ZMM3 while
vector types are returned in XMM0/YMM0/ZMM0 and integers in RAX
For more information or examples please see also:
https://msdn.microsoft.com/en-us/library/dn375768.aspx
Observations
------------------
- LLVM IR must preserve the original position of the arguments.
- Since HVA structures are allocated in lower priority than vector
types, the vector types should be allocated first. Hence, one
pass on the argument list is not sufficient anymore,...