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++/66017] Undefined behaviour in std::set<long long>
Date: Thu, 28 May 2015 12:34:00 -0000	[thread overview]
Message-ID: <bug-66017-4-7L4VDgOMtN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66017-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 28 12:33:36 2015
New Revision: 223811

URL: https://gcc.gnu.org/viewcvs?rev=223811&root=gcc&view=rev
Log:
        PR libstdc++/66017
        * include/bits/stl_tree.h (_Rb_tree_node): Use __aligned_membuf.
        (_Rb_tree_iterator, _Rb_tree_const_iterator): Support construction
        from _Base_ptr.
        (_Rb_tree_const_iterator::_M_const_cast): Remove static_cast.
        (_Rb_tree::begin, _Rb_tree::end): Remove static_cast.
        * include/ext/aligned_buffer.h (__aligned_membuf): New type using
        alignment of _Tp as a member subobject, not as a complete object.
        * python/libstdcxx/v6/printers.py (StdRbtreeIteratorPrinter): Lookup
        _Link_type manually as it might not be in the debug info.

Modified:
    branches/gcc-5-branch/libstdc++-v3/ChangeLog
    branches/gcc-5-branch/libstdc++-v3/include/bits/stl_tree.h
    branches/gcc-5-branch/libstdc++-v3/include/ext/aligned_buffer.h
    branches/gcc-5-branch/libstdc++-v3/python/libstdcxx/v6/printers.py


  parent reply	other threads:[~2015-05-28 12:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 12:04 [Bug libstdc++/66017] New: " public at hansmi dot ch
2015-05-05 12:14 ` [Bug libstdc++/66017] " public at hansmi dot ch
2015-05-05 12:17 ` public at hansmi dot ch
2015-05-21 10:27 ` redi at gcc dot gnu.org
2015-05-22 15:50 ` redi at gcc dot gnu.org
2015-05-27 11:19 ` redi at gcc dot gnu.org
2015-05-28 12:34 ` redi at gcc dot gnu.org [this message]
2015-05-28 12:36 ` redi at gcc dot gnu.org
2015-05-28 21:06 ` public at hansmi dot ch
2015-09-24 20:54 ` ctice 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-66017-4-7L4VDgOMtN@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).