From: Mike Stump <mikestump@comcast.net>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
Bernd Schmidt <bschmidt@redhat.com>,
Ulrich Weigand <uweigand@de.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ping] Fix PR debug/66728
Date: Mon, 09 Nov 2015 18:47:00 -0000 [thread overview]
Message-ID: <99FCD813-5EB8-44E3-9364-C2A5B4C3D1CE@comcast.net> (raw)
In-Reply-To: <CAFiYyc2KvBw_fhhC+MXSzzbg445tPwwSXHKiO3TLAqfqQow7NA@mail.gmail.com>
On Nov 6, 2015, at 5:06 AM, Richard Biener <richard.guenther@gmail.com> wrote:
>> If there are no substantial reasons to not check it in now, I’d like to proceed and get it checked in. People can refine it further in tree if they want. Any objections?
>
> Ok with a changelog entry and bootstrap/regtest.
Also committed to the release branch after waiting a few days to ensure no issue on trunk after the normal regression test and bootstrap.
prev parent reply other threads:[~2015-11-09 18:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 14:24 Richard Sandiford
2015-08-21 16:20 ` Jeff Law
2015-10-28 12:04 ` [ping] " Ulrich Weigand
2015-10-28 13:14 ` Richard Sandiford
2015-10-28 14:25 ` Bernd Schmidt
2015-10-28 14:58 ` Ulrich Weigand
2015-11-02 15:30 ` Richard Sandiford
2015-11-02 16:29 ` Richard Sandiford
2015-11-02 20:34 ` [ping] " Mike Stump
2015-11-02 20:55 ` Richard Sandiford
2015-11-02 23:29 ` Mike Stump
2015-11-03 8:46 ` Richard Sandiford
2015-11-03 21:59 ` Mike Stump
2015-11-04 9:43 ` Richard Biener
2015-11-04 11:58 ` Mike Stump
2015-11-04 12:15 ` Richard Biener
2015-11-04 19:36 ` Mike Stump
2015-11-04 20:51 ` Richard Sandiford
2015-11-04 23:45 ` Mike Stump
2015-11-05 12:32 ` Richard Biener
2015-11-06 1:35 ` Mike Stump
2015-11-06 13:06 ` Richard Biener
2015-11-09 18:47 ` Mike Stump [this message]
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=99FCD813-5EB8-44E3-9364-C2A5B4C3D1CE@comcast.net \
--to=mikestump@comcast.net \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=uweigand@de.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).