From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix splay tree KEY leak detected in GDB test gdb.base/macscp.exp
Date: Sun, 03 Feb 2019 17:58:00 -0000 [thread overview]
Message-ID: <1549216729.2630.17.camel@skynet.be> (raw)
In-Reply-To: <20190203104539.6272f9d8@f29-4.lan>
Thanks for looking at this.
The below change was discussed with Tom on irc.
Tom pushed a first fix in the splay tree, so it would be easier
for me if he (or someone else) could also push this one.
Thanks
Philippe
On Sun, 2019-02-03 at 10:45 -0700, Kevin Buettner wrote:
> On Sat, 26 Jan 2019 23:34:35 +0100
> Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:
>
> > include/ChangeLog
> > 2019-01-26 Philippe Waroquiers <philippe.waroquiers@skynet.be>
> >
> > * splay-tree.h (splay_tree_delete_key_fn): Update comment.
> > (splay_tree_delete_value_fn): Likewise.
> >
> > libiberty/ChangeLog
> > 2019-01-26 Philippe Waroquiers <philippe.waroquiers@skynet.be>
> >
> > * splay-tree.c (splay_tree_insert): Also release old KEY in case
> > of insertion of a key equal to an already present key.
> > (splay_tree_new_typed_alloc): Update comment.
>
> These changes look reasonable to me, BUT...
>
> I think you'll need to get approval for this patch from the gcc
> maintainers. The libiberty README file indicates that fixes should be
> sent to gcc-patches@gcc.gnu.org.
>
> Kevin
next prev parent reply other threads:[~2019-02-03 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 22:34 Philippe Waroquiers
2019-02-03 17:45 ` Kevin Buettner
2019-02-03 17:58 ` Philippe Waroquiers [this message]
2019-02-05 13:48 ` Tom Tromey
2019-02-05 19:55 ` Philippe Waroquiers
2019-02-12 13:13 ` Tom Tromey
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=1549216729.2630.17.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
/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