Mirror of the gdb-patches mailing list
 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 v2 1/8] [gdb/testsuite] allow more registers in reader test
Date: Sun, 29 Mar 2020 22:55:00 -0400	[thread overview]
Message-ID: <ef55b6d8-0e52-c6e4-9485-90d719181e81@simark.ca> (raw)
In-Reply-To: <20200327103932.17765-1-mihails.strasuns@intel.com>

On 2020-03-27 6:39 a.m., Mihails Strasuns via Gdb-patches wrote:
> Fixes jit-reader test failures on systems that have more registers than
> expected by the current condition.
> 
> gdb/testsuite/ChangeLog:
> 
> 2020-02-18  Mihails Strasuns  <mihails.strasuns@intel.com>
> 
> 	* gdb.base/jit-reader.exp: relax register output check
> 
> Signed-off-by: Mihails Strasuns <mihails.strasuns@intel.com>
> Change-Id: I227ab8691b2363d626f7100216477ab637f619fa
> ---
>  gdb/testsuite/gdb.base/jit-reader.exp | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/gdb/testsuite/gdb.base/jit-reader.exp b/gdb/testsuite/gdb.base/jit-reader.exp
> index 7852a5b550..5140e3d930 100644
> --- a/gdb/testsuite/gdb.base/jit-reader.exp
> +++ b/gdb/testsuite/gdb.base/jit-reader.exp
> @@ -92,6 +92,7 @@ proc info_registers_current_frame {sp} {
>  	     "es             $hex +$neg_decimal" \
>  	     "fs             $hex +$neg_decimal" \
>  	     "gs             $hex +$neg_decimal" \
> +	     ".*" \
>  	    ]
>  }
>  
> @@ -196,6 +197,7 @@ proc jit_reader_test {} {
>  			 "es             <not saved>" \
>  			 "fs             <not saved>" \
>  			 "gs             <not saved>" \
> +			 ".*" \
>  			]

The comment in this message was not addressed:

https://sourceware.org/pipermail/gdb-patches/2020-March/166893.html

Simon


      parent reply	other threads:[~2020-03-30  2:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <165972>
2020-03-27 10:39 ` Mihails Strasuns
2020-03-27 10:39   ` [PATCH v2 2/8] [gdb/testsuite] structured rename of jit test files Mihails Strasuns
2020-03-27 10:39   ` [PATCH v2 3/8] [gdb/testsuite] share jit-protocol.h by all jit tests Mihails Strasuns
2020-03-27 10:39   ` [PATCH v2 4/8] [gdb/testsuite] use args as lib list for jit-elf tests Mihails Strasuns
2020-03-30  3:00     ` Simon Marchi
2020-03-31 15:13       ` Strasuns, Mihails
2020-03-31 16:08         ` Simon Marchi
2020-03-27 10:39   ` [PATCH v2 5/8] [gdb/testsuite] add lib/jit-elf-helpers.exp Mihails Strasuns
2020-03-27 10:39   ` [PATCH v2 6/8] [gdb/testsuite] use -Ttext-segment for jit-elf tests Mihails Strasuns
2020-03-27 10:39   ` [PATCH v2 7/8] [gdb/testsuite] define jit function name via macro Mihails Strasuns
2020-03-27 10:39   ` [PATCH v2 8/8] [gdb/testsuite] add jit-elf-util.h and run jit function Mihails Strasuns
2020-03-30  2:55   ` Simon Marchi [this message]

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=ef55b6d8-0e52-c6e4-9485-90d719181e81@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