public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>,
	 gdb-patches@sourceware.org,
	 Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [RFC][gdb/symtab] Lazy expansion of full symbol table
Date: Sun, 20 Jun 2021 12:17:05 -0600	[thread overview]
Message-ID: <8735tcxuxq.fsf@tromey.com> (raw)
In-Reply-To: <e49aa422-8446-bb20-56c8-32dac80f5853@suse.de> (Tom de Vries's message of "Sun, 20 Jun 2021 11:41:16 +0200")

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> I found out that the precondition for using std::lower_bound of the
Tom> vector being sorted in a certain way is not valid:
[...]

While debugging a different failure today, I found that the 'find'
method wasn't waiting for the future to resolve, so it was allowing use
of the vector before it was ready.  This is fixed on the branch now.

I have 125 regressions to go.  At the same time I think part of the
quick function code still has to be rewritten; I haven't tested DWO yet;
and I am not sure all the modes that Ada supports are handled by the
lookup code.  So there's still a reasonable amount to do.  Then of
course there's the final rebasing to shape it up, the branch history is
particularly ugly at this moment.

Tom

  reply	other threads:[~2021-06-20 18:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14  9:39 Tom de Vries
2021-06-14 20:54 ` Tom Tromey
2021-06-14 23:36   ` Tom de Vries
2021-06-15 13:26     ` Tom Tromey
2021-06-16 10:20       ` Tom de Vries
2021-06-18  2:30         ` Tom Tromey
2021-06-19 19:36           ` Tom de Vries
2021-06-20  9:41             ` Tom de Vries
2021-06-20 18:17               ` Tom Tromey [this message]
2021-06-22  9:16                 ` Tom de Vries
2021-06-20 23:44             ` Tom Tromey
2021-06-21  9:18               ` Tom de Vries
2021-06-27 22:24                 ` Tom Tromey
2021-06-28  0:48               ` Tom Tromey

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=8735tcxuxq.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).