public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: snyder <snyder@fnal.gov>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10139: g++ 3.4 ICE --- memory overwrite/allocation problem?
Date: Wed, 19 Mar 2003 03:26:00 -0000 [thread overview]
Message-ID: <20030319032600.17529.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/10139; it has been noted by GNATS.
From: snyder <snyder@fnal.gov>
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 <jh@suse.cz>
* 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
next reply other threads:[~2003-03-19 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 3:26 snyder [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-18 19:26 snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030319032600.17529.qmail@sources.redhat.com \
--to=snyder@fnal.gov \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).