On Fri, 01 Jan 2010 19:31:49 +0100, Don wrote: > Moritz Warning wrote: >> On Thu, 31 Dec 2009 21:22:58 +0100, grauzone wrote: >> >>> bearophile wrote: >>>> grauzone: >>>>> But I have a problem: the compiler is either extremely slow for me, >>>>> or is stuck in an endless loop. All it does is to slowly allocate >>>>> memory. I aborted the compilation after ~ 20 minutes and 2 GB RAM >>>>> allocation. This wasn't the case with dmd 1.053, where it only took >>>>> 5-10 seconds to compile. Can anyone confirm this? >>>> Show the code! >>> I was going to say "but it's hundreds of modules", but then I tried to >>> compile some other big hog of code: Tango. >>> >>> And I found compiling this file hangs: >>> http://dsource.org/projects/tango/browser/trunk/tango/core/tools/ >> Demangler.d?rev=5248 >>> The exact command line for this was: >>> dmd -c -I../tango/core -I.. -I../tango/core/vendor -release >>> -oftango-core-tools-Demangler-release.o >>> ../tango/core/tools/Demangler.d >>> >>> Again, could anyone confirm this? >>> >>> Anyway, no time for this anymore, it's going to be 2010 soon here. >>> >>>> Bye, >>>> bearophile >> Someone reported the regression already: >> >> http://d.puremagic.com/issues/show_bug.cgi?id=3663 > > It's caused by the patch for bug 400.
Thanks, that fixed it. But now there is another problem/regression: tango/net/device/Berkeley.d(1065): Error: enum member tango.net.device.Berkeley.IPv4Address.ADDR_ANY conflicts with enum member tango.net.device.Berkeley.IPv4Address.ADDR_ANY at tango/net/device/ Berkeley.d(1065) tango/net/device/Berkeley.d(1066): Error: enum member tango.net.device.Berkeley.IPv4Address.ADDR_NONE conflicts with enum member tango.net.device.Berkeley.IPv4Address.ADDR_NONE at tango/net/ device/Berkeley.d(1066) tango/net/device/Berkeley.d(1067): Error: enum member tango.net.device.Berkeley.IPv4Address.PORT_ANY conflicts with enum member tango.net.device.Berkeley.IPv4Address.PORT_ANY at tango/net/device/ Berkeley.d(1067)