From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: rguenther@suse.de
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Proposal to postpone release of 5.2 for a week
Date: Fri, 10 Jul 2015 09:54:00 -0000 [thread overview]
Message-ID: <20150710.185412.08267308.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <alpine.LSU.2.11.1507101126250.9923@zhemvz.fhfr.qr>
Richard Biener <rguenther@suse.de> wrote:
>> Can I backport the patch in
>>
>> [SH] Fix PR target/66780
>> https://gcc.gnu.org/ml/gcc-patches/2015-07/msg00472.html
>>
>> to gcc-5.2? It's a few lines change for a SH specific wrong code bug
>> with -fstack-protector which is disastrous for Debian SH folks who use
>> that option heavily in their packages.
>
> Yes.
Thanks! I've just committed it as revision 225660.
Regards,
kaz
next prev parent reply other threads:[~2015-07-10 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 20:20 Proposal to postpone release of 5.2 for a week [Was: Re: patch to fix PR66782] Uros Bizjak
2015-07-10 8:09 ` Richard Biener
2015-07-10 8:48 ` Proposal to postpone release of 5.2 for a week Kaz Kojima
2015-07-10 9:26 ` Richard Biener
2015-07-10 9:54 ` Kaz Kojima [this message]
2015-07-10 13:20 ` Proposal to postpone release of 5.2 for a week [Was: Re: patch to fix PR66782] Vladimir Makarov
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=20150710.185412.08267308.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).