public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: make use of scoped_restore in unduplicated_should_be_inserted
Date: Thu, 20 Oct 2022 15:45:52 +0000 (GMT)	[thread overview]
Message-ID: <20221020154552.8C06E3850211@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aaa141a0a99fb63f6209da75257c58d94404a963

commit aaa141a0a99fb63f6209da75257c58d94404a963
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Wed Oct 5 10:21:02 2022 +0100

    gdb: make use of scoped_restore in unduplicated_should_be_inserted
    
    I noticed that we could make use of a scoped_restore in the function
    unduplicated_should_be_inserted.  I've also converted the function
    return type from int to bool.
    
    This change shouldn't make any difference, as I don't think anything
    within should_be_inserted could throw an exception, but the change
    doesn't hurt, and will help keep us safe if anything ever changes in
    the future.
    
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

Diff:
---
 gdb/breakpoint.c | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 84eeccd0cd7..bfa017f1398 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -2299,16 +2299,13 @@ should_be_inserted (struct bp_location *bl)
 /* Same as should_be_inserted but does the check assuming
    that the location is not duplicated.  */
 
-static int
+static bool
 unduplicated_should_be_inserted (struct bp_location *bl)
 {
-  int result;
-  const int save_duplicate = bl->duplicate;
+  scoped_restore restore_bl_duplicate
+    = make_scoped_restore (&bl->duplicate, 0);
 
-  bl->duplicate = 0;
-  result = should_be_inserted (bl);
-  bl->duplicate = save_duplicate;
-  return result;
+  return should_be_inserted (bl);
 }
 
 /* Parses a conditional described by an expression COND into an

                 reply	other threads:[~2022-10-20 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221020154552.8C06E3850211@sourceware.org \
    --to=aburgess@sourceware.org \
    --cc=gdb-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).