Displaying 2 results from an estimated 2 matches for "sseregparm".
2016 Mar 03
2
RFC: Implementing the Swift calling convention in LLVM and Clang
...LLVM really can’t just decide to use a different register
once there’s an agreed interpretation. It sounds like the problem you were
running into with “inreg” was that the ARM backend didn’t have a stable meaning
for it, probably because the ARM target doesn’t allow the frontend features
(regparm/sseregparm) that inreg is designed for. But there are targets — i386,
chiefly — where inreg has a defined, stable meaning precisely because regparm
has a defined, stable meaning. It seems to me that an abi(“context”) attribute
would be more like the latter than the former: any target that supports swiftcc
w...
2016 Mar 03
2
RFC: Implementing the Swift calling convention in LLVM and Clang
> On Mar 3, 2016, at 2:00 AM, Renato Golin <renato.golin at linaro.org> wrote:
>
> On 2 March 2016 at 20:03, John McCall <rjmccall at apple.com> wrote:
>> We don’t need to. We don't use the intermediary convention’s rules for aggregates.
>> The Swift rule for aggregate arguments is literally “if it’s too complex according to
>> <foo>, pass it