public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "Strasuns, Mihails" <mihails.strasuns@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v5 1/5] [gdb/testsuite] use args as lib list for jit-elf tests
Date: Tue, 12 May 2020 10:13:31 -0400	[thread overview]
Message-ID: <2baf41dc-717b-e81e-ebe3-084c229da68c@simark.ca> (raw)
In-Reply-To: <MWHPR11MB0048D296BB1D554242774DE495BE0@MWHPR11MB0048.namprd11.prod.outlook.com>

On 2020-05-12 3:51 a.m., Strasuns, Mihails wrote:
> Fixed nits for the series and pushed. Thank you for your patience!

Thanks for _your_ patience, this has taken a while because of me, thanks
for pushing through.

If I recall, the initial goal of this was to fix some JIT bug in GDB itself,
and these test refactorings were to make it possible to write a test for that?

Simon


  reply	other threads:[~2020-05-12 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167782>
2020-05-11 10:28 ` Mihails Strasuns
2020-05-11 10:28   ` [PATCH v5 2/5] [gdb/testsuite] add lib/jit-elf-helpers.exp Mihails Strasuns
2020-05-12  0:23     ` Simon Marchi
2020-05-11 10:28   ` [PATCH v5 3/5] [gdb/testsuite] use -Ttext-segment for jit-elf tests Mihails Strasuns
2020-05-12  0:28     ` Simon Marchi
2020-05-11 10:28   ` [PATCH v5 4/5] [gdb/testsuite] define jit function name via macro Mihails Strasuns
2020-05-12  0:31     ` Simon Marchi
2020-05-11 10:28   ` [PATCH v5 5/5] [gdb/testsuite] add jit-elf-util.h and run jit function Mihails Strasuns
2020-05-12  0:37     ` Simon Marchi
2020-05-12  0:17   ` [PATCH v5 1/5] [gdb/testsuite] use args as lib list for jit-elf tests Simon Marchi
2020-05-12  7:51     ` Strasuns, Mihails
2020-05-12 14:13       ` Simon Marchi [this message]
2020-05-12 14:15         ` 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=2baf41dc-717b-e81e-ebe3-084c229da68c@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=mihails.strasuns@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).