This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: transactional-memory status
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, "Joseph S. Myers" <joseph at codesourcery dot com>, Jakub Jelinek <jakub at redhat dot com>, Torvald Riegel <triegel at redhat dot com>, Richard Henderson <rth at redhat dot com>
- Date: Mon, 7 Nov 2011 23:55:53 +0100
- Subject: Re: transactional-memory status
- References: <4EB84672.6070101@redhat.com>
On Mon, Nov 7, 2011 at 9:58 PM, Aldy Hernandez <aldyh@redhat.com> wrote:
> Dear Release Managers...
>
> We're pretty much done with the merge blockers, and even suggestions that
> weren't blockers :). ?The only outstanding patch review is a cleanup by
> Richard Henderson that is waiting for Richi's review here:
>
> http://gcc.gnu.org/ml/gcc-patches/2011-11/msg01033.html
>
> I am still testing some whitespace changes, but I'm fairly confident in my
> ability to hit tab and space bar.
>
> Is there anything else you require of me?
>
> Ideally I'd like a slush, if the merge gets approved. ?I would do one last
> trunk->branch, test, apply the global diff to trunk, and ask for a slush
> while I commit. ?This is, assuming the merge is authorized. ?I could also
> post the last diff before the commit, if it is necessary.
>
> What do you guys think?
I suppose we can freeze for the TM merge once we leave stage1 (thus,
in a few hours).
If you are ready by then, of course, and the tree isn't too broken.
Richard.