[llvm-commits] [PATCH] Bug in APCS
Eric Christopher
echristo at apple.com
Tue Oct 12 14:04:22 PDT 2010
On Oct 12, 2010, at 1:55 PM, Chris Lattner wrote:
>
> On Oct 12, 2010, at 1:51 PM, Eric Christopher wrote:
>
>>>> Sure, but what do you think should happen with the return value? Seems like whatever generated the arg passing in the first place should have done the right thing?
>>>
>>> I'm not sure what you mean. The code generator shouldn't crash on IR that returns a <3 x double>. Codegen should do something sensible even though it isn't constrained to match a specific ABI.
>>
>> Sure, I'd prefer it raise an error if it's a type that it can't handle conformantly rather than generate code that's unexpected.
>
> What frontend/language are you assuming? Not all frontends have types that are defined by the ABI. The code generator should still do something useful with them.
:)
Custom/New ABI then? This seems pretty clearly not what the ABI says for an object of > 128-bits. What do we do for other such things in X86 4xfloat or something?
-eric
More information about the llvm-commits
mailing list