Bug 1746 – Enums with member initializers generate undefined symbols

Steps to reproduce: ----- bug.d ----- module bug; enum GDCBUG { BUG = -1, ISSUE = -2, PROBLEM = -3 } ----------------- Compile with: gdmd -S bug.d Test with: cat bug.s | grep __s Output: .long ___s.898 .local ___s.898 .comm ___s.898,0,1 ======================== WORKAROUND: ----- bug.d ----- module bug; enum GDCBUG { GDC_WORKAROUND, //If the first member has no default value (or that value is 0), no undefined symbols are produced. BUG = -1, ISSUE = -2, PROBLEM = -3 } ----------------- Compile with: gdmd -S bug.d Test with: cat bug.s | grep __s Output: (empty) ======================== First experienced by the Tango guys: http://dsource.org/projects/tango/ticket/450 Now causing lots of problems for the gtkD guys: http://www.dsource.org/projects/gtkd/ticket/4 This still happens in gdc-0.25-4.1.2-17 from Debian Lenny.

Added to DStress as http://dstress.kuehne.cn/run/e/enum_52_A.d http://dstress.kuehne.cn/run/e/enum_52_B.d http://dstress.kuehne.cn/run/e/enum_52_C.d

Still happens on revision 199 (with debian etch, x86_64)

Fixed in release 0.25 / svn 213. Not sure if the description or the DStress cases actually test the problem(?) Need to have two modules: -- a.d -- enum E { A = 1, B = 2 } -- b.d -- import a; void main() { new E[10]; } --