public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Plan to merge LRA.
Date: Fri, 19 Oct 2012 14:42:00 -0000	[thread overview]
Message-ID: <50816425.20103@redhat.com> (raw)

   I'd like to commit LRA patches on the Sunday.  I got a lot of 
feedback about LRA for a few last weeks.  All patches besides RA part 
were approved by Jeff Law.  Steven Bosscher and I solved LRA speed 
problem on famous PR54146.  Now Steven does not object to LRA merge.

   I got invaluable reviews of LRA parts from Richard Sandiford.  I 
guess Richard thought deeply about reload for a long time.  His 
proposals were very useful and made LRA code much more clear.

   I'd like to thank all these people for their help and spending a lot 
of time on reviews and LRA work.

   So my plan is to merge trunk into LRA branch first and, if it looks 
ok, commit LRA to the trunk on Sunday to be ready solve problems (if 
there are any) starting Monday morning EST.  LRA merge will affect only 
x86/x86-64 target.  If you suspect any problem with LRA and have no 
quick response from me, you can easily switch it off by putting false 
instead of true in function i386.c::lra_p and continue your work until 
the problem is solved by me.

   The work on LRA will be continued on the branch.  There are still few 
proposals non-critical for x86/x86-64 which will be implemented on the 
branch.  After some stabilization of LRA branch for other targets, it 
would be nice if target maintainers look at the branch. It will make 
transitions of more targets to LRA more smoothly when development of 
gcc4.9 starts.

Vlad.

             reply	other threads:[~2012-10-19 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 14:42 Vladimir Makarov [this message]
2012-10-19 15:58 ` Diego Novillo
2012-10-19 16:05   ` Vladimir Makarov
2012-10-19 16:17     ` Diego Novillo

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=50816425.20103@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).