Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Pedro Alves <pedro@palves.net>,
	Simon Marchi <simon.marchi@efficios.com>,
	 gdb-patches@sourceware.org
Cc: Laurent <Laurent.Morichetti@amd.com>
Subject: Re: [PATCH 4/4] gdb: change regcache list to be a map
Date: Wed, 5 Aug 2020 16:25:35 -0400	[thread overview]
Message-ID: <56bd04f4-1c55-ab51-e80e-d320858a5d47@simark.ca> (raw)
In-Reply-To: <27f7abde-0118-efee-6001-6b4b8f2d46a8@palves.net>

On 2020-08-05 2:02 p.m., Pedro Alves wrote:
> On 7/30/20 6:03 PM, Simon Marchi wrote:
>> On 2020-07-30 12:58 p.m., Simon Marchi wrote:
>>> It's down to:
>>>
>>>        for (auto it = regcaches.begin (); it != regcaches.end ();)
>>> 	 {
>>> 	   if (it->second->target () == target)
>>> 	     it = regcaches.erase (it);
>>> 	   else
>>> 	     it++;
>>> 	 }
>> Ah, I see that you've provided me a patch for that too (I thought you only
>> did the multi-level map thing).
> Note that it's idiomatic to write ++it instead of it++, to avoid
> creating a temporary.  It's possible that compilers nowadays optimize
> it away, but it still looks odd to not write ++it to me.

Ack.

>
>   Your code is:
>>         for (auto it = regcaches.begin (); it != regcaches.end ();)
>>           {
>>             if (it->second->target () == target)
>>               {
>>                 delete it->second;
>>                 it = regcaches.erase (it);
>>               }
>>           }
>>
>> I think you are missing an it++ in the else?  Otherwise, when the target doesn't
>> match, we'll get into an infinite loop I presume.
> Yes, I was.  I didn't notice because I jumped straight to the multi-map
> patch on top, which deletes that code, IIRC.
>
Thanks.

Simon



  reply	other threads:[~2020-08-05 20:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 20:40 [PATCH 0/4] Regcache fix and optimization Simon Marchi
2020-07-20 20:40 ` [PATCH 1/4] gdb: rename regcache::current_regcache to regcache::regcaches Simon Marchi
2020-07-23 20:01   ` Pedro Alves
2020-07-20 20:40 ` [PATCH 2/4] gdb: move regcache::regcaches to regcache.c Simon Marchi
2020-07-23 20:03   ` Pedro Alves
2020-07-20 20:41 ` [PATCH 3/4] gdb: pass target to thread_ptid_changed observable Simon Marchi
2020-07-23 20:42   ` Pedro Alves
2020-07-30 15:27     ` Simon Marchi
2020-08-05 14:50       ` Pedro Alves
2020-08-05 19:08         ` Simon Marchi
2020-08-05 22:29           ` Pedro Alves
2020-07-20 20:41 ` [PATCH 4/4] gdb: change regcache list to be a map Simon Marchi
2020-07-24  1:53   ` Pedro Alves
2020-07-24 16:59     ` John Baldwin
2020-07-30 16:26       ` Simon Marchi
2020-07-30 16:58     ` Simon Marchi
2020-07-30 17:03       ` Simon Marchi
2020-08-05 18:02         ` Pedro Alves
2020-08-05 20:25           ` Simon Marchi [this message]
2020-07-30 17:07       ` Simon Marchi
2020-07-30 18:17     ` Simon Marchi
2020-08-05 18:14       ` Pedro Alves
2020-08-10 19:15   ` Tom Tromey
2020-08-10 19:25     ` Simon Marchi
2020-08-12 12:52   ` Tom Tromey
2020-08-12 15:17     ` Tom Tromey
2020-08-06 20:27 ` [PATCH 0/4] Regcache fix and optimization 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=56bd04f4-1c55-ab51-e80e-d320858a5d47@simark.ca \
    --to=simark@simark.ca \
    --cc=Laurent.Morichetti@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=simon.marchi@efficios.com \
    /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