Displaying 2 results from an estimated 2 matches for "byvalalign".
2012 Mar 30
2
[LLVMdev] [cfe-commits] Fix handling of ARM homogenous aggregates
...ependent 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 believe that if...
2012 Apr 04
0
[LLVMdev] [cfe-commits] Fix handling of ARM homogenous aggregates
...ependent 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 believe that if...