From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>,
Mihails Strasuns <mihails.strasuns@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] [gdb/testsuite] structured rename of jit test files
Date: Sat, 21 Mar 2020 22:47:38 -0400 [thread overview]
Message-ID: <013699e3-9f9f-b312-e0d1-c42b34d19a9d@simark.ca> (raw)
In-Reply-To: <871rqqs242.fsf@tromey.com>
On 2020-02-19 4:23 p.m., Tom Tromey wrote:
>>>>>> "Mihails" == Mihails Strasuns <mihails.strasuns@intel.com> writes:
>
> Mihails> Reorganizes how JIT related test files to be more clear what are related
> Mihails> to JIT reader system tests and what use JIT from ELF objfiles. Those two
> Mihails> approaches are quite different in GDB implementation and require very
> Mihails> different test setup. Keeping distinction clear at the file name level
> Mihails> makes it easier to maintain the testsuite.
>
> Mihails> gdb/testsuite/ChangeLog:
>
> Mihails> 2020-02-18 Mihails Strasuns <mihails.strasuns@intel.com>
>
> Mihails> * gdb.base: rename all jit related test and source files
>
> Ok. Thanks.
>
> Tom
>
LGTM from me too, that's a good idea, thanks.
Simon
next prev parent reply other threads:[~2020-03-22 2:47 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 [this message]
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
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=013699e3-9f9f-b312-e0d1-c42b34d19a9d@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=mihails.strasuns@intel.com \
--cc=tom@tromey.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