Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org,  tdevries@suse.de,
	 cbiesinger@google.com,  philippe.waroquiers@skynet.be,
	 andrew.burgess@embecosm.com,  tom@tromey.com
Subject: Re: GDB 9.1 release -- 2019-11-18 Update
Date: Tue, 19 Nov 2019 16:10:00 -0000	[thread overview]
Message-ID: <878sobyhhl.fsf@tromey.com> (raw)
In-Reply-To: <20191119011235.GD2568@adacore.com> (Joel Brobecker's message of	"Mon, 18 Nov 2019 17:12:35 -0800")

Joel> As in the previous update, we can use the "for-9.1" tag to identify patches
Joel> that we think should go in GDB 9.1. Here is the URL to the corresponding
Joel> dashboard:

I added one more today.  It's a small patch that fixes a crash.

Joel>  - 11 patches that no longer apply ("Merge Conflict") :-(

This is actually the normal state due to ChangeLog files.
I just ignore that column.

Joel>   - [Tom DV] Prefer var def over decl
Joel>     https://sourceware.org/ml/gdb-patches/2019-09/msg00161.html
Joel>     Gerrit: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/29

Joel>     Tom T said the patch is reasonable, but was wondering whether
Joel>     we shouldn't even be in that situation in the first place, if
Joel>     we were to not create symbols for declarations...  This lead to
Joel>     a different patch, but after discussion, we propose the original
Joel>     patch for trunk to start, and then discuss the alternative
Joel>     approach after 9.x branching. Joel is double-checking with
Joel>     TomT that this is OK with him as well.

I will look at this either today or tomorrow.

Joel>   - [Christian B] The threaded symbol loading that tromey Christian have been working on
Joel>     Gerrit: https://gnutoolchain-gerrit.osci.io/r/q/topic:%22minsyms-threads%22+(status:open%20OR%20status:merged)

Joel>     This patchset was identified as a risk for inclusion so close
Joel>     to branching, due to the use of threads for parallelizing
Joel>     the load of minsyms. However, considering the potentially massive
Joel>     gains to be had on large programs, the consensus was to allow
Joel>     this patch under the control of a setting, off by default; and
Joel>     then remove that setting once we've branched.

I must have missed this discussion.  I saw Christian had a patch to do
this, but I think maybe it can be done more simply... I will
investigate.

Joel>   - [TomT] Fix the "winheight" command
Joel>     https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/371

Joel>     Fixes a regression.
Joel>     Tom says it can be backported after branching if needed.

I'll send a smaller version of this that doesn't involve rewriting all
of the TUI layout code.

Joel>   - [TomT] Handle pending stops from the Windows kernel
Joel>     Gerrit: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/414
Joel>   - [TomT] Add pending stop support to gdbserver's Windows port
Joel>     Gerrit: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/432
Joel>     Fixes an internal-error.

These two are the same series, I'm re-investigating now.

Tom


  reply	other threads:[~2019-11-19 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  1:12 Joel Brobecker
2019-11-19 16:10 ` Tom Tromey [this message]
2019-11-19 19:06   ` Tom Tromey
2019-11-24 18:16 ` Philippe Waroquiers

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=878sobyhhl.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=brobecker@adacore.com \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    --cc=tdevries@suse.de \
    /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