From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Propose GDB 10 branch this Fri-Sun (Sep 11-13) [2020-09-05 Update]
Date: Sat, 5 Sep 2020 13:53:18 -0700 [thread overview]
Message-ID: <20200905205318.GA30158@adacore.com> (raw)
Hi everyone,
Below is another status update before branching. We're almost there,
and if all goes well, I propose we create the branch during the weekend
of Fri-Sun Sep 11-13, immediately followed by creating the first
prerelease.
Fixed Since the Previous Update:
--------------------------------
<none>
Added Since the Last Update:
----------------------------
<none> (Yay! ;-) )
Other Ongoing Items:
--------------------
* [TomT/HannesD] <PR win32/25302>
Mismatching fstat() function calls in gdb_bfd_open() and cache_bstat()
https://sourceware.org/bugzilla/show_bug.cgi?id=25302
Latest discussion at:
https://sourceware.org/pipermail/gdb-patches/2020-June/169670.html
https://sourceware.org/pipermail/gdb-patches/2020-July/170681.html
https://sourceware.org/pipermail/gdb-patches/2020-August/171249.html
Tom sent a patch locally changing gnulib (reviewed and OK-ed by
yours truly, but with a request to wait a bit before getting it in):
https://sourceware.org/pipermail/gdb-patches/2020-September/171660.html
* [TomT] <PR rust/26197>
rust FAILs with rustc 1.36.0 and llvm 7
https://sourceware.org/bugzilla/show_bug.cgi?id=26197
Patch pushed:
https://sourceware.org/pipermail/gdb-patches/2020-July/170764.html
At the stage where we are just XFAIL-ing the remaining failures.
I'd say we have the most important part of the fix, and whatever
is left can easily be backported to the branch if needed.
Not Critical, but Requested:
----------------------------
<none>
Cheers!
--
Joel
next reply other threads:[~2020-09-05 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 20:53 Joel Brobecker [this message]
2020-09-07 0:07 ` Kamil Rytarowski
2020-09-07 20:02 ` Simon Marchi
2020-09-08 13:49 ` Joel Brobecker
2020-09-08 13:51 ` Kamil Rytarowski
2020-09-10 15:01 ` Simon Marchi
2020-09-08 15:40 ` Christian Biesinger
2020-09-08 17:06 ` Joel Brobecker
2020-09-10 15:03 ` Simon Marchi
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=20200905205318.GA30158@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).