Eric Blake wrote:
> My recollection from using the proprietary Green Hills Software compiler
> for PowerPC at work was that they implemented va_list as a one-element
> array of a struct. They provided va_copy with their latest 4.x version
> compiler, but in the 3.x version, my workaround for implementing va_copy
> for their compiler ended up looking like:
>
> #define gl_va_copy(a,b) ((a)[0] = (b)[0])
>
> I don't know if it is worth trying to detect this in your .m4
If the problems comes up with another compiler as well, there will be two ways
to solve it:
a) change the gl_va_copy definition to use memcpy instead of an assignment,
b) recognize the case of an array type and in this case provide the
va_copy function ourselves.
Bruno
