This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/50858] [4.7 Regression] segfault at ../../gcc/libiberty/hashtab.c:981
- From: "markus at trippelsdorf dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 24 Oct 2011 21:23:35 +0000
- Subject: [Bug c++/50858] [4.7 Regression] segfault at ../../gcc/libiberty/hashtab.c:981
- Auto-submitted: auto-generated
- References: <bug-50858-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50858
--- Comment #4 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2011-10-24 21:23:35 UTC ---
(In reply to comment #2)
> What do you mean by 'probably'? Did you bisect this?
By probably I mean looking at the backtrace and running
git-blame starting from the top entry. Then one finally arrives at:
/../gcc/gcc/cp/call.c:2587 which points to your commit:
71c20982 (paolo 2011-10-14 14:43:03 +0000 2587) tree cptype =
composite_pointer_type (type1, type2,
I did revert the commit later and this "solves" the issue.