public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ctice at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66521] xgcc: cc1plus segfaults when compiling libstdc++-v3/src/c++11/ostream-inst.cc
Date: Tue, 28 Jul 2015 17:01:00 -0000	[thread overview]
Message-ID: <bug-66521-4-EWkArB19oT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66521-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66521

--- Comment #4 from ctice at gcc dot gnu.org ---
Created attachment 36082
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36082&action=edit
Tentative patch to fix this issue.

I believe the attached patch will fix this problem.  I would appreciate it if
Eric would confirm that.

ChangeLogs:

gcc/cp/ChangeLog:

        * mangle.c : Add vtable-verify.h to include files.
        (get_mangled_vtable_map_var_name):  If the DECL_ASSEMBLER_NAME
        is "<anon>" get the real mangled name for the class instead, and
        also store the real mangled name in a vector for use later.

gcc/ChangeLog:

        * vtable-verify.c (vtbl_mangled_name_types, vtbl_mangled_name_ids): New
        global variables.
        (vtbl_find_mangled_name):  New function.
        (vtbl_register_mangled_name):  New function.
        (vtbl_map_get_node):  If DECL_ASSEMBLER_NAME is "<anon>", look up
        mangled name in mangled name vectors.
        (find_or_create_vtbl_map_node):  Ditto.
        (var_is_used_for_virtual_call_p):  Add recursion_depth parameter;
        update recursion_depth on function entry; pass it to every recursive
        call; automatically exit if depth > 25 (give up looking at that point).
        (verify_bb_vtables):  Initialize recursion_depth and pass it to
        var_is_used_for_virtual_call_p.
        * vtable-verify.h (vtbl_mangbled_name_types, vtbl_mangled_name_ids):
New
        global variable decls.
        (vtbl_register_mangled_name): New extern function decl.


libvtv/ChangeLog:

        * Makefile.am:  Update to match latest tree.
        * Makefile.in: Regenerate.
        * testsuite/lib/libvtv: Brought up to date.
        * vtv_malloc.cc (VTV_DEBUG): Update function call to match renamed
        function (old bug!).
        * vtv_rts.cc (debug_functions, debug_init, debug_verify_vtable): Update
        initializations to work correctly with VTV_DEBUG defined.


  parent reply	other threads:[~2015-07-28 17:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 13:42 [Bug bootstrap/66521] New: " egall at gwmail dot gwu.edu
2015-06-12 13:45 ` [Bug bootstrap/66521] " egall at gwmail dot gwu.edu
2015-07-05  4:04 ` egall at gwmail dot gwu.edu
2015-07-06 16:02 ` ctice at gcc dot gnu.org
2015-07-28 17:01 ` ctice at gcc dot gnu.org [this message]
2015-07-30 12:08 ` redi at gcc dot gnu.org
2015-07-30 12:11 ` redi at gcc dot gnu.org
2015-07-30 14:10 ` egall at gwmail dot gwu.edu
2015-07-31 15:25 ` egall at gwmail dot gwu.edu
2015-08-05 18:41 ` egall at gwmail dot gwu.edu
2015-08-05 18:44 ` egall at gwmail dot gwu.edu
2015-08-07 23:18 ` cmtice at google dot com
2015-08-12 15:40 ` ctice at gcc dot gnu.org
2015-08-30 18:21 ` egall at gwmail dot gwu.edu
2015-08-30 18:38 ` egall at gwmail dot gwu.edu

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=bug-66521-4-EWkArB19oT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).