From: Tom Tromey <tom@tromey.com>
To: Mihails Strasuns <mihails.strasuns@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/7] [gdb/testsuite] share jit-protocol.h by all jit tests
Date: Wed, 19 Feb 2020 21:23:00 -0000 [thread overview]
Message-ID: <87wo8iqnj6.fsf@tromey.com> (raw)
In-Reply-To: <20200218124339.11270-4-mihails.strasuns@intel.com> (Mihails Strasuns's message of "Tue, 18 Feb 2020 13:43:35 +0100")
>>>>> "Mihails" == Mihails Strasuns <mihails.strasuns@intel.com> writes:
Mihails> There was an existing jit-protocol.h defining common symbols needed for
Mihails> JIT-supporting application, however, it was only used by few tests.
Mihails> Others redeclared the same symbols.
Mihails> This unifies all tests to use jit-protocol.h
Mihails> gdb/testsuite/ChangeLog:
Mihails> 2020-02-18 Mihails Strasuns <mihails.strasuns@intel.com>
Mihails> * gdb.base/jit-attach-pie.c: use jit-protocol.h
Mihails> * gdb.base/jit-elf-main.c: use jit-protocol.h
Mihails> * gdb.base/jit-reader-host.c: use jit-protocol.h
Mihails> * gdb.base/jit-reader-simple-jit.c: use jit-protocol.h
Mihails> * gdb.base/jit-protocol.h: update definitions to match all usage
Mihails> contexts
Thank you for doing this. This is ok.
Tom
next prev parent reply other threads:[~2020-02-19 21:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 12:42 [PATCH 0/7] refactor and enhance jit testing Mihails Strasuns
2020-02-18 12:42 ` [PATCH 2/7] [gdb/testsuite] structured rename of jit test files Mihails Strasuns
2020-02-19 21:23 ` Tom Tromey
2020-03-22 2:47 ` Simon Marchi
2020-02-18 12:42 ` [PATCH 7/7] [gdb/testsuite] add jit-elf-util.h and run jit function Mihails Strasuns
2020-03-23 3:13 ` Simon Marchi
2020-03-23 9:23 ` Strasuns, Mihails
2020-03-23 11:14 ` Simon Marchi
2020-02-18 12:42 ` [PATCH 6/7] [gdb/testsuite] use -Ttext-segment for jit-elf tests Mihails Strasuns
2020-03-23 3:03 ` Simon Marchi
2020-02-18 12:42 ` [PATCH 4/7] [gdb/testsuite] use args as lib list " Mihails Strasuns
2020-03-23 0:04 ` Simon Marchi
2020-03-23 0:35 ` Simon Marchi
2020-02-18 12:42 ` [PATCH 1/7] [gdb/testsuite] allow more registers in reader test Mihails Strasuns
2020-02-19 21:22 ` Tom Tromey
2020-03-21 16:03 ` Simon Marchi
2020-03-22 2:09 ` Simon Marchi
2020-02-18 12:42 ` [PATCH 3/7] [gdb/testsuite] share jit-protocol.h by all jit tests Mihails Strasuns
2020-02-19 21:23 ` Tom Tromey [this message]
2020-03-22 16:00 ` Simon Marchi
2020-02-18 12:42 ` [PATCH 5/7] [gdb/testsuite] add lib/jit-elf-helpers.exp Mihails Strasuns
2020-03-23 0:52 ` Simon Marchi
2020-02-26 13:56 ` [PATCH 0/7] refactor and enhance jit testing Strasuns, Mihails
2020-03-18 12:48 ` 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=87wo8iqnj6.fsf@tromey.com \
--to=tom@tromey.com \
--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