public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51365] cannot use final empty class in std::tuple
Date: Sun, 28 Apr 2013 11:40:00 -0000	[thread overview]
Message-ID: <bug-51365-4-ll36SeWL9H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51365-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51365

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.8.1                       |4.9.0

--- Comment #17 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-04-28 11:40:24 UTC ---
shared_ptr fixed to handle final allocators by:

Author: redi
Date: Sun Apr 28 11:38:21 2013
New Revision: 198367

URL: http://gcc.gnu.org/viewcvs?rev=198367&root=gcc&view=rev
Log:
    PR libstdc++/51365
    * include/bits/shared_ptr_base (_Sp_ebo_helper): Helper class to
    implement EBO safely.
    (_Sp_counted_base::_M_get_deleter): Add noexcept.
    (_Sp_counter_ptr): Use noexcept instead of comments.
    (_Sp_counted_deleter): Likewise. Use _Sp_ebo_helper.
    (_Sp_counted_ptr_inplace): Likewise.
    * testsuite/20_util/shared_ptr/cons/51365.cc: New.
    * testsuite/20_util/shared_ptr/cons/52924.cc: Add rebind member to
    custom allocator and test construction with custom allocator.
    * testsuite/20_util/shared_ptr/cons/43820_neg.cc: Adjust dg-error
    line number.

Added:
    trunk/libstdc++-v3/testsuite/20_util/shared_ptr/cons/51365.cc
      - copied, changed from r198365,
trunk/libstdc++-v3/testsuite/20_util/shared_ptr/cons/52924.cc
Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/include/bits/shared_ptr_base.h
    trunk/libstdc++-v3/testsuite/20_util/shared_ptr/cons/43820_neg.cc
    trunk/libstdc++-v3/testsuite/20_util/shared_ptr/cons/52924.cc


  parent reply	other threads:[~2013-04-28 11:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 19:22 [Bug libstdc++/51365] New: " redi at gcc dot gnu.org
2011-11-30 19:34 ` [Bug libstdc++/51365] " redi at gcc dot gnu.org
2011-11-30 19:40 ` paolo.carlini at oracle dot com
2011-11-30 21:26 ` redi at gcc dot gnu.org
2011-11-30 21:30 ` redi at gcc dot gnu.org
2011-11-30 21:30 ` redi at gcc dot gnu.org
2011-11-30 23:51 ` redi at gcc dot gnu.org
2011-12-01  1:07 ` redi at gcc dot gnu.org
2011-12-03 12:06 ` redi at gcc dot gnu.org
2011-12-11 12:55 ` marc.glisse at normalesup dot org
2011-12-11 13:51 ` redi at gcc dot gnu.org
2011-12-11 13:56 ` marc.glisse at normalesup dot org
2011-12-15 10:06 ` redi at gcc dot gnu.org
2011-12-15 10:10 ` redi at gcc dot gnu.org
2011-12-20  9:14 ` redi at gcc dot gnu.org
2012-02-04 13:54 ` redi at gcc dot gnu.org
2013-03-22 14:45 ` jakub at gcc dot gnu.org
2013-04-28 11:40 ` redi at gcc dot gnu.org [this message]
2014-04-22 11:36 ` jakub at gcc dot gnu.org
2014-04-22 14:36 ` redi at gcc dot gnu.org

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-51365-4-ll36SeWL9H@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).