From: Vladimir Makarov <vmakarov@redhat.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [lra] resync with trunk
Date: Mon, 14 Jan 2013 16:13:00 -0000 [thread overview]
Message-ID: <50F42EB3.4040504@redhat.com> (raw)
In-Reply-To: <CABu31nOFeC3Mq8XB2pv6kHD4tOsbr0kUDMEs5siymD55GZ97Mg@mail.gmail.com>
On 13-01-11 5:39 PM, Steven Bosscher wrote:
> Hello Vlad,
>
> The attached patch back-ports to the LRA branch (or foward-ports,
> depending on how you look at it :-) all the changes made on the trunk
> to LRA.
>
> Bootstrapped&tested on powerpc64-unknown-linux-gnu[1] and
> ia64-unknown-linux-gnu[2], and cross-built and tested mipsisa64-elf
> [3].
>
> [1] http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01098.html
> [2] http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01129.html
> [3] http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01120.html
>
> OK for the LRA branch?
>
>
Yes. Thanks for this and installing automatic LRA branch testing, Steven.
prev parent reply other threads:[~2013-01-14 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 22:40 Steven Bosscher
2013-01-14 16:13 ` Vladimir Makarov [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=50F42EB3.4040504@redhat.com \
--to=vmakarov@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb.gcc@gmail.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).