This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 6.5 Status Report (2018-10-19)
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 25 Oct 2018 18:40:57 +0200
- Subject: Re: GCC 6.5 Status Report (2018-10-19)
- References: <20181019095433.GR11625@tucnak> <CAH6eHdSqM_pOwhf8aB721_cCB1m_X=K2sJWfK9jpUWcJxiRJwQ@mail.gmail.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Oct 25, 2018 at 05:32:56PM +0100, Jonathan Wakely wrote:
> On Fri, 19 Oct 2018 at 10:54, Jakub Jelinek <jakub@redhat.com> wrote:
> >
> > Status
> > ======
> >
> > The 6.5 branch is now frozen for the final GCC 6.5 release, the release
> > candidate has been announced. All changes to the branch require RM
> > approval.
>
> Since the branch was frozen I was made aware of two libstdc++
> regressions that affect all active branches. They're fixed everywhere
> except gcc-6-branch, these are the patches:
>
> https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01602.html
> https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01599.html
>
> It's not the end of the world if they don't get fixed for 6.5, but if
> it's not too late I'd like to commit them both.
Ok.
Jakub