From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fix hashtable memory leak
Date: Tue, 27 Nov 2018 22:00:00 -0000 [thread overview]
Message-ID: <20181127220041.GD809@redhat.com> (raw)
In-Reply-To: <d7093394-f8af-6c81-0262-afc593a31867@gmail.com>
On 27/11/18 22:31 +0100, François Dumont wrote:
>I eventually called the new method _M_assign_elements.
Perfect.
>And yes, tracker_allocator was enough.
Great.
>Committed on trunk for the moment.
Great, thanks.
Please note that GCC 7.4 RC1 is scheduled for this week:
https://gcc.gnu.org/ml/gcc/2018-11/msg00118.html
Will you be able to backport the simpler patch (without the
refactoring to remove code duplication) to the branch before then?
If not I can take care of it.
next prev parent reply other threads:[~2018-11-27 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:23 François Dumont
2018-11-24 21:58 ` François Dumont
2018-11-26 12:03 ` Jonathan Wakely
2018-11-26 12:35 ` Jonathan Wakely
2018-11-26 12:12 ` Jonathan Wakely
2018-11-27 21:31 ` François Dumont
2018-11-27 22:00 ` Jonathan Wakely [this message]
2018-11-28 6:36 ` François Dumont
2018-11-28 10:42 ` Jonathan Wakely
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=20181127220041.GD809@redhat.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).