Re: GDB 7.10 release 2015-07-17 status update?

[Luis Machado <lgustavo@codesourcery.com>]

Hi Joel,

On 07/17/2015 02:53 PM, Joel Brobecker wrote:
> Hello,
>
> It's been almost 2 weeks since we branched, and there has been a number
> of issues fixed since then.
>
> On the wiki (https://sourceware.org/gdb/wiki/GDB_7.10_Release),
> we have 1 TODO item left:
>
>    - Eval with KeithS regressions due to GCC 5.1 (regressions caused by
>      GCC rather than GDB)
>
>      For this one, the latest (private) update I got from Keith was
>      that GDB was likely in the clear - mostly GCC issues? Keith?
>
> We still have 2 "Maybe"'s:
>
>    - [GCC review/Jan] PR compile/18485 (set debug compile: Display GCC driver
>      filename)
>    - [GCC review/Jan] PR compile/18486 (Add 'set compile-gcc')
>
>    If the reason for it being a "Maybe" is time, we can probably give you
>    a little extra time (see below).
>
> I've moved the following item to the Exclude list, as per Pedro's
> recommendation:
>
>    - PR gdb/18600 (After forking and threads spawning, gdb leaves newly
>      created threads stopped) (too delicate)
>
> David Edelson reported that the buildBot was reporting a lot of
> failures around the time we cut the branch. Has anyone looked at those
> since then? When I did, I was looking at the waterfall view, and
> several builds looked like they were failing right at the beginning,
> so I didn't know what to make of it. Also, that's a lot of info to
> grok, so I didn't have time to look further.
>
> What I can say is that I've tested the branch with a number of
> platforms, not as exhaustively of course, but so far, it looks
> pretty good.
>
> What I think we should do is give it another couple of weeks, and
> see if other reports come up. It would be good, also, if we had
> some info about the buildBOT failures, and whether the release
> might be affected by any regression it found.
>
> So, I propose a re-sync on Aug 3rd.
>

Do we consider the fact that mingw32 (and maybe other non-GNU) builds 
have been broken since this libiberty sync a blocker/critical issue?

https://sourceware.org/ml/gdb-patches/2015-06/msg00405.html

Last we heard of it was here...

https://sourceware.org/ml/gdb-patches/2015-06/msg00654.html

But we received no word from Yunlian Jiang yet.

Maybe it should be added to the wiki too?