public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Mihails Strasuns <mihails.strasuns@intel.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v3 4/9] [gdb/testsuite] use args as lib list for jit-elf tests
Date: Fri, 17 Apr 2020 22:58:16 -0400	[thread overview]
Message-ID: <49eaa7a6-b124-c15b-b1fe-17a7d72833ff@simark.ca> (raw)
In-Reply-To: <20200331171356.26126-4-mihails.strasuns@intel.com>

On 2020-03-31 1:13 p.m., Mihails Strasuns via Gdb-patches wrote:
> @@ -106,49 +106,38 @@ int mypid;
>  int
>  MAIN (int argc, char *argv[])
>  {
> -  /* These variables are here so they can easily be set from jit.exp.  */
> -  const char *libname = NULL;
> -  int count = 0, i, fd;
> -  struct stat st;
> -
> +  int i;
>    alarm (300);
> +  char* fake_argv[10]; // used as backing storage for GDB to populate argv

Space goes before the start: `char *fake_argv`.  For comments, please follow the
usual style:

- Capital letter and period (two spaces after the final period).
- On the line before, not the same line.
- /* */, not //

> @@ -146,31 +149,23 @@ proc one_jit_test {count match_str reattach} {
>      }
>  }
>  
> -if {[compile_jit_test jit.exp "" {}] < 0} {
> -    return
> -}
> -one_jit_test 1 "${hex}  jit_function_0000" 0
> -one_jit_test 2 "${hex}  jit_function_0000\[\r\n\]+${hex}  jit_function_0001" 0
> +compile_jit_main "" {}
> +compile_n_jit_so 2

I mentioned ealier: if we fail to compile the test program, we don't want to execute the rest
of the test case.  That's what the previous code did.  Can you keep that?

Simon

  reply	other threads:[~2020-04-18  2:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166773>
2020-03-31 17:13 ` [PATCH v3 1/9] [gdb/testsuite] allow more registers in reader test Mihails Strasuns
2020-03-31 17:13   ` [PATCH v3 2/9] [gdb/testsuite] structured rename of jit test files Mihails Strasuns
2020-04-18  2:35     ` Simon Marchi
2020-03-31 17:13   ` [PATCH v3 3/9] [gdb/testsuite] share jit-protocol.h by all jit tests Mihails Strasuns
2020-04-18  2:38     ` Simon Marchi
2020-03-31 17:13   ` [PATCH v3 4/9] [gdb/testsuite] use args as lib list for jit-elf tests Mihails Strasuns
2020-04-18  2:58     ` Simon Marchi [this message]
2020-04-20  7:35       ` Strasuns, Mihails
2020-04-20 13:08         ` Simon Marchi
2020-04-20 13:53           ` Simon Marchi
2020-03-31 17:13   ` [PATCH v3 5/9] [gdb/testsuite] add lib/jit-elf-helpers.exp Mihails Strasuns
2020-03-31 17:13   ` [PATCH v3 6/9] [gdb/testsuite] use -Ttext-segment for jit-elf tests Mihails Strasuns
2020-03-31 17:13   ` [PATCH v3 7/9] [gdb/testsuite] define jit function name via macro Mihails Strasuns
2020-03-31 17:13   ` [PATCH v3 8/9] [gdb/testsuite] add jit-elf-util.h and run jit function Mihails Strasuns
2020-03-31 17:13   ` [PATCH v3 9/9] [gdb/testsuite] handle compilation failures in jit-elf-helpers Mihails Strasuns
2020-04-14 10:08   ` [PATCH v3 1/9] [gdb/testsuite] allow more registers in reader test Strasuns, Mihails
2020-04-18  2:30   ` 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=49eaa7a6-b124-c15b-b1fe-17a7d72833ff@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).