Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: cbiesinger@chromium.org
Cc: gdb-patches@sourceware.org,  Christian Biesinger <cbiesinger@google.com>
Subject: Re: [FYI/PUSHED] Revert "Turn off threaded minsym demangling by default"
Date: Fri, 13 Dec 2019 23:16:00 -0000	[thread overview]
Message-ID: <87blsbvmt0.fsf@tromey.com> (raw)
In-Reply-To: <20191213224519.113253-1-cbiesinger@chromium.org>	(cbiesinger@chromium.org's message of "Fri, 13 Dec 2019 17:45:19	-0500")

>>>>> ">" == cbiesinger  <cbiesinger@chromium.org> writes:

>> As agreed on the mailing list, now that GDB 9 has branched, this patch
>> reverts the change to set worker-threads to zero. After this patch,
>> multithreaded minsym demangling will be enabled again by default.

Thanks.  I think maybe the docs needed a tweak as well?

Tom


  reply	other threads:[~2019-12-13 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 22:45 cbiesinger
2019-12-13 23:16 ` Tom Tromey [this message]
2019-12-14 18:23   ` Christian Biesinger via gdb-patches
2019-12-16 19:17     ` Pedro Alves
2019-12-20  0:25       ` Christian Biesinger via gdb-patches

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=87blsbvmt0.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=cbiesinger@chromium.org \
    --cc=cbiesinger@google.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