From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8976 invoked by alias); 22 Jul 2004 03:33:05 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 8969 invoked by uid 48); 22 Jul 2004 03:33:05 -0000 Date: Thu, 22 Jul 2004 03:33:00 -0000 Message-ID: <20040722033305.8968.qmail@sourceware.org> From: "bkoz at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040718123236.16614.peturr02@ru.is> References: <20040718123236.16614.peturr02@ru.is> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/16614] Excessive resource usage in __mt_alloc X-Bugzilla-Reason: CC X-SW-Source: 2004-07/txt/msg02619.txt.bz2 List-Id: ------- Additional Comments From bkoz at gcc dot gnu dot org 2004-07-22 03:33 ------- Compiling this ICEs mainline. It takes about 8 minutes with 3.4.1, and uses 700-800MB. The resulting executables run fine. I've separated out the common data, and inherited from this for the rest of __mt_alloc. This does allow mainline to compile and run. This does have an immediate linkage improvement, comparable performance, and keeps the ability to tune pool characteristics, although not on a per-type basis. If this ability is considered important, it would probably be more interesting to have a policy based design that would allow both a shared and individual (per-type) pools. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16614