public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: gcc@gcc.gnu.org
Cc: Richard Guenther <richard.guenther@gmail.com>,
	        Cary Coutant <ccoutant@google.com>
Subject: Status of LTO merge to mainline
Date: Tue, 07 Jul 2009 13:10:00 -0000	[thread overview]
Message-ID: <b798aad50907070609m6d017a32l742a4a07e939724a@mail.gmail.com> (raw)

I am working on the last 60 testsuite failures on x86_64, but I'm
sure there will be other failures in other architectures.  My
merge plan is:

1- Fix the remaining failures on x86_64.  This includes fixing
   thunks for vararg functions which I plan to address as
   outlined in http://gcc.gnu.org/ml/gcc-patches/2008-12/msg00953.html

2- Fix open PRs against the LTO branch.  There are 28 open bugs
   against the branch.  I need to triage them to see which ones
   may already be fixed.

3- Enable pass_ipa_free_lang_data by default.  This is the pass
   that removes all references to front end trees from GIMPLE,
   implicitly breaking debugging information.  My current plan is
   to implement Richi's and Cary's idea of generating debug info
   early.

4- Test on primary and secondary platforms.  What is the current
   suggested list of platforms?


The items that need active development are #1 and #3.  For #1, I
think I can have all the failures fixed in 2-3 weeks.  I do not
have a good estimate for #3 since I do not really know how much
work this will entail (Richi?  Cary?  would you have a rough
estimate for this?).

Any and all help I can get with #2 and #4 will be appreciated.
For #2, I need to triage the reports to see which ones can be
closed already.  For #4, it should be a matter of testing the
branch with:

$ svn co svn://gcc.gnu.org/svn/gcc/branches/lto
$ mkdir bld && cd bld
$ ../lto/configure --enable-lto && make && make -k check


Thanks.  Diego.

             reply	other threads:[~2009-07-07 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 13:10 Diego Novillo [this message]
2009-07-07 13:31 ` H.J. Lu
2009-07-07 13:36   ` Diego Novillo
2009-07-07 13:37   ` Richard Guenther
2009-07-08  7:15 ` Kaveh R. GHAZI
2009-07-08 12:12   ` Diego Novillo
2009-07-13 10:43     ` Richard Earnshaw
2009-07-13 10:51       ` Diego Novillo
2009-07-14 19:27     ` Joseph S. Myers

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=b798aad50907070609m6d017a32l742a4a07e939724a@mail.gmail.com \
    --to=dnovillo@google.com \
    --cc=ccoutant@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@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).