From: Joel Brobecker <brobecker@adacore.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR 18669: Remove use of strtod in libiberty/d-demangle.c
Date: Tue, 04 Aug 2015 17:24:00 -0000 [thread overview]
Message-ID: <20150804172415.GJ4777@adacore.com> (raw)
In-Reply-To: <CABOHX+cOqzqZFOxY-qsaLye36otzmbwT_L0cgSZ8yzpMLx7UrA@mail.gmail.com>
> By the way, would this also be a candidate for the 7.10 branch?
> Assume that upstream GCC respond in a timely manner. :-)
It looks to me like this would only affect D support, and
the patch seems innocent enough that, yes, it would be OK to push
to the branch as well.
We're still waiting for a couple of issues to be resolved
(at least). So you still have a bit of time. I've found that
libiberty changes are usually reviewed pretty quick, so hopefully
you'll be OK. Ping me when I start talking about creating the release
if necessary.
--
Joel
next prev parent reply other threads:[~2015-08-04 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 14:24 Iain Buclaw
2015-08-04 17:07 ` Joel Brobecker
2015-08-04 17:16 ` Iain Buclaw
2015-08-04 17:24 ` Joel Brobecker [this message]
2015-08-05 15:51 ` Iain Buclaw
2015-08-11 6:48 ` Iain Buclaw
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=20150804172415.GJ4777@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.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