search for: byvalsize

...o the target-dependent backend code for it to do the right thing. By the time the target is involved, all that remains of any composite type is: * The fields completely separated if it was naturally by value. {float, float} just gives you two "float" parameters for example. * i32, the ByValSize and ByValAlign if it was a byval pointer: e.g. "{float, float}* byval". Even in the first case there's no indication of where a composite type begins and ends. The latter could be bludgeoned to mean "this is an HFA, put it in VFP regs", but it would be unspeakably ugly. I...

...o the target-dependent backend code for it to do the right thing. By the time the target is involved, all that remains of any composite type is: * The fields completely separated if it was naturally by value. {float, float} just gives you two "float" parameters for example. * i32, the ByValSize and ByValAlign if it was a byval pointer: e.g. "{float, float}* byval". Even in the first case there's no indication of where a composite type begins and ends. The latter could be bludgeoned to mean "this is an HFA, put it in VFP regs", but it would be unspeakably ugly. I...

Attached is a working patch set for llvm to be able to emit arm64 (currently as triple aarch64-apple-ios) mach-o object files, in case someone is interested. I'm not sure if the llvm maintainers want the patch given the previous message that there's going to be an official patch set from apple to support this, but here is mine. What works (tested on an iPhone 5S): * objc strings,