public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Use new and delete in jit.c Date: Wed, 6 Apr 2022 20:22:26 +0000 (GMT) [thread overview] Message-ID: <20220406202226.038D73858D37@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8fb105930851c7a722b4794f8348f72f29721cd0 commit 8fb105930851c7a722b4794f8348f72f29721cd0 Author: Tom Tromey <tom@tromey.com> Date: Tue Apr 5 14:43:30 2022 -0600 Use new and delete in jit.c This changes jit.c to use new and delete, rather than XCNEW. This simplifies the code a little. This was useful for another patch I'm working on, and I thought it would make sense to send it separately. Regression tested on x86-64 Fedora 34. Diff: --- gdb/jit.c | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/gdb/jit.c b/gdb/jit.c index a727143e68b..342b0d07114 100644 --- a/gdb/jit.c +++ b/gdb/jit.c @@ -935,7 +935,7 @@ struct jit_unwind_private { /* Cached register values. See jit_frame_sniffer to see how this works. */ - detached_regcache *regcache; + std::unique_ptr<detached_regcache> regcache; /* The frame being unwound. */ struct frame_info *this_frame; @@ -1002,10 +1002,7 @@ static void jit_dealloc_cache (struct frame_info *this_frame, void *cache) { struct jit_unwind_private *priv_data = (struct jit_unwind_private *) cache; - - gdb_assert (priv_data->regcache != NULL); - delete priv_data->regcache; - xfree (priv_data); + delete priv_data; } /* The frame sniffer for the pseudo unwinder. @@ -1035,11 +1032,11 @@ jit_frame_sniffer (const struct frame_unwind *self, gdb_assert (!*cache); - *cache = XCNEW (struct jit_unwind_private); - priv_data = (struct jit_unwind_private *) *cache; + priv_data = new struct jit_unwind_private; + *cache = priv_data; /* Take a snapshot of current regcache. */ - priv_data->regcache = new detached_regcache (get_frame_arch (this_frame), - true); + priv_data->regcache.reset + (new detached_regcache (get_frame_arch (this_frame), true)); priv_data->this_frame = this_frame; callbacks.priv_data = priv_data; @@ -1072,7 +1069,7 @@ jit_frame_this_id (struct frame_info *this_frame, void **cache, struct gdb_reader_funcs *funcs; struct gdb_unwind_callbacks callbacks; - priv.regcache = NULL; + priv.regcache.reset (); priv.this_frame = this_frame; /* We don't expect the frame_id function to set any registers, so we
reply other threads:[~2022-04-06 20:22 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=20220406202226.038D73858D37@sourceware.org \ --to=tromey@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: linkBe 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).