public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "devans at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65839] xmethods need updating once gdb decides how to fix 18285
Date: Wed, 29 Apr 2015 22:51:00 -0000	[thread overview]
Message-ID: <bug-65839-4-ok90QoMwTi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65839-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from devans at gcc dot gnu.org ---
Author: devans
Date: Wed Apr 29 22:50:31 2015
New Revision: 222599

URL: https://gcc.gnu.org/viewcvs?rev=222599&root=gcc&view=rev
Log:
        PR libstdc++/65839
        * python/libstdcxx/v6/xmethods.py (get_bool_type): New function.
        Replace all lookups of "bool" with this.
        (get_std_size_type): New function.  Replace all lookups of std::size_t
        with this.
        (*Worker): New method get_result_type.
        (DequeWorkerBase.__init__): New arg val_type.  All callers updated.
        (ListWorkerBase.__init__): New arg val_type.  All callers updated.
        (UniquePtrGetWorker.__init__): New arg elem_type.  All callers updated.
        Delete setting of name, enabled.
        (UniquePtrDerefWorker.__init__): New arg elem_type.  All callers
        updated.  Delete setting of name.
        (UniquePtrMethodsMatcher): Rewrite for consistency with all other
        libstdc++ xmethod matchers.
        * testsuite/libstdc++-xmethods/array.cc: Add whatis tests.
        * testsuite/libstdc++-xmethods/associative-containers.cc: Ditto.
        * testsuite/libstdc++-xmethods/deque.cc: Ditto.
        * testsuite/libstdc++-xmethods/forwardlist.cc: Ditto.
        * testsuite/libstdc++-xmethods/list.cc: Ditto.
        * testsuite/libstdc++-xmethods/unique_ptr.cc: Ditto.
        * testsuite/libstdc++-xmethods/vector.cc: Ditto.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/python/libstdcxx/v6/xmethods.py
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/array.cc
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/associative-containers.cc
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/deque.cc
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/forwardlist.cc
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/list.cc
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/unique_ptr.cc
    trunk/libstdc++-v3/testsuite/libstdc++-xmethods/vector.cc


  parent reply	other threads:[~2015-04-29 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 22:32 [Bug libstdc++/65839] New: " dje at google dot com
2015-04-21 23:38 ` [Bug libstdc++/65839] " redi at gcc dot gnu.org
2015-04-21 23:48 ` dje at google dot com
2015-04-27 22:40 ` dje at google dot com
2015-04-29 22:51 ` devans at gcc dot gnu.org [this message]
2015-05-26 21:29 ` devans at gcc dot gnu.org
2015-05-26 21:46 ` dje at google dot com

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-65839-4-ok90QoMwTi@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).