From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 7/9] gdb/jit: remove jiter_objfile_data -> objfile back-link
Date: Wed, 15 Jul 2020 10:16:35 +0200 [thread overview]
Message-ID: <240cef6206625251ffa32c3b0a4d85bef1755480.1594799616.git.tankut.baris.aktemur@intel.com> (raw)
In-Reply-To: <cover.1594799616.git.tankut.baris.aktemur@intel.com>
In-Reply-To: <cover.1594799616.git.tankut.baris.aktemur@intel.com>
From: Simon Marchi <simon.marchi@polymtl.ca>
This is no longer needed, remove it.
gdb/ChangeLog:
2020-MM-DD Simon Marchi <simon.marchi@polymtl.ca>
* objfiles.h (struct jiter_objfile_data) <jiter_objfile_data>:
Remove.
<objfile>: Remove.
* jit.c (get_jiter_objfile_data): Update.
---
gdb/jit.c | 2 +-
gdb/objfiles.h | 7 -------
2 files changed, 1 insertion(+), 8 deletions(-)
diff --git a/gdb/jit.c b/gdb/jit.c
index 87872ac9018..e15b67107af 100644
--- a/gdb/jit.c
+++ b/gdb/jit.c
@@ -254,7 +254,7 @@ static jiter_objfile_data *
get_jiter_objfile_data (objfile *objf)
{
if (objf->jiter_data == nullptr)
- objf->jiter_data.reset (new jiter_objfile_data (objf));
+ objf->jiter_data.reset (new jiter_objfile_data ());
return objf->jiter_data.get ();
}
diff --git a/gdb/objfiles.h b/gdb/objfiles.h
index d508f3fab52..e5828618dfe 100644
--- a/gdb/objfiles.h
+++ b/gdb/objfiles.h
@@ -412,15 +412,8 @@ class separate_debug_range
struct jiter_objfile_data
{
- jiter_objfile_data (struct objfile *objfile)
- : objfile (objfile)
- {}
-
~jiter_objfile_data ();
- /* Back-link to the objfile. */
- struct objfile *objfile;
-
/* Symbol for __jit_debug_register_code. */
minimal_symbol *register_code = nullptr;
--
2.17.1
next prev parent reply other threads:[~2020-07-15 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 8:16 [PATCH v3 0/9] Handling multiple JITers Tankut Baris Aktemur
2020-07-15 8:16 ` [PATCH v3 1/9] gdb/jit: pass the jiter objfile as an argument to jit_event_handler Tankut Baris Aktemur
2020-07-15 13:48 ` Simon Marchi
2020-07-21 16:24 ` Aktemur, Tankut Baris
2020-07-15 8:16 ` [PATCH v3 2/9] gdb/jit: link to jit_objfile_data directly from the objfile struct Tankut Baris Aktemur
2020-07-15 14:16 ` Simon Marchi
2020-07-21 16:25 ` Aktemur, Tankut Baris
2020-07-21 17:42 ` Simon Marchi
2020-07-15 8:16 ` [PATCH v3 3/9] gdb/jit: split jit_objfile_data in two Tankut Baris Aktemur
2020-07-15 14:19 ` Simon Marchi
2020-07-21 16:24 ` Aktemur, Tankut Baris
2020-07-15 8:16 ` [PATCH v3 4/9] gdb/jit: apply some simplifications and assertions Tankut Baris Aktemur
2020-07-15 8:16 ` [PATCH v3 5/9] gdb/jit: move cached_code_address and jit_breakpoint to jiter_objfile_data Tankut Baris Aktemur
2020-07-15 8:16 ` [PATCH v3 6/9] gdb/jit: enable tracking multiple JITer objfiles Tankut Baris Aktemur
2020-07-15 8:16 ` Tankut Baris Aktemur [this message]
2020-07-15 8:16 ` [PATCH v3 8/9] gdb/jit: apply minor cleanup and modernization Tankut Baris Aktemur
2020-07-15 8:16 ` [PATCH v3 9/9] gdb/jit: skip jit symbol lookup if already detected the symbols don't exist Tankut Baris Aktemur
2020-07-19 15:44 ` [PATCH v3 0/9] Handling multiple JITers 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=240cef6206625251ffa32c3b0a4d85bef1755480.1594799616.git.tankut.baris.aktemur@intel.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb-patches@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).