Bug 1013 – Invalid code generated for naked functions with (u)long arguments

On x86 systems, gdc creates nonsensical code at the beginning of naked functions taking long or ulong arguments. It reserves space on the stack, and copies any long arguments to that space, thus defeating assembler code that would work in any function without long arguments. See URL for an example.

The problem appears to be that the type information records for (u)long arguments call for 64bit alignment even on architectures that do not have 64bit memory access instructions (such as x86). I haven't had the chance to find out whether the gcc "tree" structures that contain the relevant data are being produced by gdc glue code, or whether they come from the gcc middle layer or backend. David? IMHO this should be fixed for non-naked functions as well, since copying around 64bit arguments even on architectures that do not benefit from 64bit alignment, creates useless overhead.

Fixed in release 0.23

Thanks David, great work

Added to DStress as http://dstress.kuehne.cn/run/a/asm_naked_01.d