From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17544 invoked by alias); 19 Mar 2003 03:26:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 17530 invoked by uid 71); 19 Mar 2003 03:26:00 -0000 Date: Wed, 19 Mar 2003 03:26:00 -0000 Message-ID: <20030319032600.17529.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: snyder Subject: Re: c++/10139: g++ 3.4 ICE --- memory overwrite/allocation problem? Reply-To: snyder X-SW-Source: 2003-03/txt/msg01250.txt.bz2 List-Id: The following reply was made to PR c++/10139; it has been noted by GNATS. From: snyder To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jh@suse.cz Subject: Re: c++/10139: g++ 3.4 ICE --- memory overwrite/allocation problem? Date: 18 Mar 2003 21:17:38 -0600 hi - This crash seems to be related to this change to libiberty/hashtab.c: 2003-12-03 Jan Hubicka * hashtab.c (htab_expand): Fix warning. * hashtab.c (htab_expand): Compute the size of hashtable based on the number of elements actually used. (htab_traverse): Call htab_expand when table is too empty. If i back out that change, then the problem goes away for my testcase, as well as for the original source from which i extracted it. In addition, since sending this report, i've run into a couple other similar, mysterious SEGVs in gcc; reverting this change fixes those crashes too. sss