delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
X-Recipient: | djgpp-workers AT delorie DOT com |
Message-ID: | <47580E5A.2040004@iki.fi> |
Date: | Thu, 06 Dec 2007 16:59:38 +0200 |
From: | Andris Pavenis <andris DOT pavenis AT iki DOT fi> |
User-Agent: | Thunderbird 2.0.0.9 (Windows/20071031) |
MIME-Version: | 1.0 |
To: | djgpp-workers AT delorie DOT com |
Subject: | Re: gcc-4.3. snapshots and DJGPP memory allocator efficiency |
References: | <47571B5D DOT 5090305 AT iki DOT fi> |
In-Reply-To: | <47571B5D.5090305@iki.fi> |
Reply-To: | djgpp-workers AT delorie DOT com |
Andris Pavenis kirjoitti: > There seem to be serious performance problems in GCC-4.3 for DJGPP due > to slowness of free() call especially for Ada compiler. > > Tried to bootstrap gcc-4.3-20071130 for DJGPP (after reverting some > earlier changes in libiberty/configure.ac present in snapshot). > Initially thought that compiler (gnat1.exe) has went into some > infinite loop when compiling gcc/ada/ali.adb for stage2. > > Found that extremly long time is being spent in libibrty/hashtab.c in > procedure htab_delete() which in that case uses free() to release > several millions allocated memory block. htab_delete() took perhaps > about 30 minutes on Intel Core 2 Quad 2.4GHz processor (I did not > measure accuratelly). There is of course not much use of 4 processor > cores as DJGPP cannot use them all. > > Currently I see that perhaps the same thing happens (I haven't > verified with debugger) when compiling gcc/ada/g-catiio.adb (killed > after about 60 minutes, I don't know how much it will still would > require) gcc/ada/catiio.ads is perhaps a different problem: http://gcc.gnu.org/ml/gcc/2007-11/msg00791.html
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |