public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/9] Handling multiple JITers
Date: Tue, 21 Jul 2020 20:06:02 +0200	[thread overview]
Message-ID: <cover.1595354297.git.tankut.baris.aktemur@intel.com> (raw)

Hi,

This is v4 of the series originally submitted at

  https://sourceware.org/pipermail/gdb-patches/2020-May/168959.html

On top of v3, which is available at

  https://sourceware.org/pipermail/gdb-patches/2020-July/170434.html

this version addresses Simon's comments.  The most significant change
is that `jiter_objfile_data` and `jited_objfile_data` structs have been
moved to `jit.h` from `objfiles.h`.  The other changes are minor format
fixes.

The patches are also available at

  https://github.com/barisaktemur/gdb/commits/multi-jit-v4

Regards.
Baris

Simon Marchi (7):
  gdb/jit: link to jit_objfile_data directly from the objfile struct
  gdb/jit: split jit_objfile_data in two
  gdb/jit: apply some simplifications and assertions
  gdb/jit: move cached_code_address and jit_breakpoint to
    jiter_objfile_data
  gdb/jit: remove jiter_objfile_data -> objfile back-link
  gdb/jit: apply minor cleanup and modernization
  gdb/jit: skip jit symbol lookup if already detected the symbols don't
    exist

Tankut Baris Aktemur (2):
  gdb/jit: pass the jiter objfile as an argument to jit_event_handler
  gdb/jit: enable tracking multiple JITer objfiles

 gdb/breakpoint.c                             |   3 +-
 gdb/jit.c                                    | 351 +++++++------------
 gdb/jit.h                                    |  43 ++-
 gdb/objfiles.h                               |  15 +
 gdb/testsuite/gdb.base/jit-reader-simple.exp |  43 ++-
 5 files changed, 236 insertions(+), 219 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-07-21 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 18:06 Tankut Baris Aktemur [this message]
2020-07-21 18:06 ` [PATCH v4 1/9] gdb/jit: pass the jiter objfile as an argument to jit_event_handler Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 2/9] gdb/jit: link to jit_objfile_data directly from the objfile struct Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 3/9] gdb/jit: split jit_objfile_data in two Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 4/9] gdb/jit: apply some simplifications and assertions Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 5/9] gdb/jit: move cached_code_address and jit_breakpoint to jiter_objfile_data Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 6/9] gdb/jit: enable tracking multiple JITer objfiles Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 7/9] gdb/jit: remove jiter_objfile_data -> objfile back-link Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 8/9] gdb/jit: apply minor cleanup and modernization Tankut Baris Aktemur
2020-07-21 18:06 ` [PATCH v4 9/9] gdb/jit: skip jit symbol lookup if already detected the symbols don't exist Tankut Baris Aktemur
2020-07-22 12:48 ` [PATCH v4 0/9] Handling multiple JITers Simon Marchi
2020-07-22 14:03   ` Aktemur, Tankut Baris

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=cover.1595354297.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).