[llvm-commits] [patch] Fix va_arg for double and some cleanups

[Dan Gohman]

On Jul 6, 2010, at 2:41 PM, Rafael Espindola wrote:

> One issues is that we would produce silly code like
> 
>         add     r0, r0, #3
>         bfc     r0, #0, #2
> 
> for the vaarg of i32. What is the correct way to find the minimum
> alignment of an argument? This is not the same as the stack alignment
> at function entry. For example, for ARM the correct value is 4, since
> values smaller than 32 bits are promoted (see 5.2.1.1 and 5.2.1.2 in
> AAPCS).

Is TargetData::getCallFrameTypeAlignment what you want here?

Dan