public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63698] [5 Regression] std::set leaks nodes on assignment
Date: Mon, 03 Nov 2014 23:04:00 -0000	[thread overview]
Message-ID: <bug-63698-4-KbAt9j4LKB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63698-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from François Dumont <fdumont at gcc dot gnu.org> ---
Yes, looks like I had forgotten node with only a left child, too bad. My
initial plan was to use existing tree node algos in tree.cc but erase could not
be done without rebalancing which was useless for what we are doing in this
case.

So, do you take care of applying this or do you want me to submit a complete
patch on libstdc++ with your test ?
>From gcc-bugs-return-465676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 03 23:30:19 2014
Return-Path: <gcc-bugs-return-465676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29661 invoked by alias); 3 Nov 2014 23:30:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29609 invoked by uid 48); 3 Nov 2014 23:30:16 -0000
From: "thopre01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/61887] vect.exp UNRESOLVED tests
Date: Mon, 03 Nov 2014 23:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: regression
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thopre01 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-61887-4-UEHQkuWRM1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61887-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61887-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg00148.txt.bz2
Content-length: 473

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida887

thopre01 at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thopre01 at gcc dot gnu.org

--- Comment #3 from thopre01 at gcc dot gnu.org ---
"git grep slp testsuite" doesn't show me any directive looking for dump with a
slp extension so I guess this is solved?


  parent reply	other threads:[~2014-11-03 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31  9:15 [Bug libstdc++/63698] New: std::set leaks nodes on assignement adl at lrde dot epita.fr
2014-10-31  9:45 ` [Bug libstdc++/63698] [5 Regression] std::set leaks nodes on assignment redi at gcc dot gnu.org
2014-10-31 11:46 ` redi at gcc dot gnu.org
2014-10-31 12:53 ` redi at gcc dot gnu.org
2014-10-31 13:40 ` redi at gcc dot gnu.org
2014-10-31 14:09 ` redi at gcc dot gnu.org
2014-11-03 23:04 ` fdumont at gcc dot gnu.org [this message]
2014-11-05 19:16 ` fdumont 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-63698-4-KbAt9j4LKB@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).