view tests/mini/vararg4.d @ 978:6a32d2e18175

Fix a latent bug in the asm code. I think that technically, using "*m0" instead of "*0" allows LLVM to pick between using the same memory as output 0 and using a new memory location. (So far I haven't been able to construct a testcase that actually breaks because of this, though)
author Frits van Bommel <fvbommel wxs.nl>
date Wed, 18 Feb 2009 03:38:12 +0100
parents 1bb99290e03a
children
line wrap: on
line source

module vararg4;
import tango.core.Vararg;
extern(C) int printf(char*, ...);

void vafunc(...)
{
    foreach(i,v; _arguments) {
        if (typeid(byte) == v) {
            printf("byte(%d)\n", va_arg!(byte)(_argptr));
        }
        else if (typeid(short) == v) {
            printf("short(%d)\n", va_arg!(short)(_argptr));
        }
        else if (typeid(int) == v) {
            printf("int(%d)\n", va_arg!(int)(_argptr));
        }
        else if (typeid(long) == v) {
            printf("long(%ld)\n", va_arg!(long)(_argptr));
        }
        else if (typeid(float) == v) {
            printf("float(%f)\n", va_arg!(float)(_argptr));
        }
        else if (typeid(double) == v) {
            printf("double(%f)\n", va_arg!(double)(_argptr));
        }
        else if (typeid(real) == v) {
            printf("real(%f)\n", va_arg!(real)(_argptr));
        }
        else
        assert(0, "unsupported type");
    }
}

void main()
{
    vafunc(byte.max,short.max,1,2,3,4L,5.0f,6.0,cast(real)7);
}