From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Use std::vector for moribund_locations
Date: Wed, 04 Jul 2018 04:55:00 -0000 [thread overview]
Message-ID: <87lgarpplh.fsf@tromey.com> (raw)
In-Reply-To: <cefea308-68e0-228d-c6b4-1fd9db52ce83@simark.ca> (Simon Marchi's message of "Wed, 4 Jul 2018 00:51:38 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> Just a note that this changes an "unordered remove" to an "ordered remove".
Simon> If we don't need to keep the relative order of the remaining elements, it
Simon> might be good performance-wise to keep the original behavior. This could
Simon> be done by keeping the original code structure (iterating by index) and
Simon> calling undordered_remove.
Somewhere else, Pedro pointed out the unordered_remove template function
in common/gdb_vecs.h.
Tom
next prev parent reply other threads:[~2018-07-04 4:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 19:23 Tom Tromey
2018-07-03 14:46 ` Andrew Burgess
2018-07-04 4:51 ` Simon Marchi
2018-07-04 4:55 ` Tom Tromey [this message]
2018-07-04 17:39 ` Simon Marchi
2018-07-09 17:10 ` Tom Tromey
2018-07-11 1:21 ` 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=87lgarpplh.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).