From: Simon Marchi <simon.marchi@polymtl.ca>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix is_amd64_regs_target check in i386-avx512.exp
Date: Mon, 01 Oct 2018 16:04:00 -0000 [thread overview]
Message-ID: <109ef268e8076ad4b46fd6bb0b793432@polymtl.ca> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B236B36026E@IRSMSX104.ger.corp.intel.com>
On 2018-10-01 05:49, Metzger, Markus T wrote:
> Hello Simon,
>
>> As reported by Jan here:
>>
>> https://sourceware.org/ml/gdb-patches/2018-09/msg00831.html
>>
>> the check that sets the number of available registers seems backwards.
>> I can't test this patch however, since I don't have access to a cpu
>> with AVX512.
>> Could somebody perhaps from Intel, or somebody else that has access to
>> such
>> CPU, take a look?
>
> It indeed is backwards.
>
> The current test fails badly when run with -m32.
>
>
>> gdb/testsuite/ChangeLog:
>>
>> * gdb.arch/i386-avx512.exp: Fix setting of nr_regs based on
>> is_amd64_regs_target.
>> ---
>> gdb/testsuite/gdb.arch/i386-avx512.exp | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/gdb/testsuite/gdb.arch/i386-avx512.exp
>> b/gdb/testsuite/gdb.arch/i386-avx512.exp
>> index de2f62c3e1f..f27af534cfd 100644
>> --- a/gdb/testsuite/gdb.arch/i386-avx512.exp
>> +++ b/gdb/testsuite/gdb.arch/i386-avx512.exp
>> @@ -93,9 +93,9 @@ gdb_test "break [gdb_get_line_number "third
>> breakpoint
>> here"]" \ gdb_continue_to_breakpoint "continue to third breakpoint in
>> main"
>>
>> if [is_amd64_regs_target] {
>> - set nr_regs 8
>> -} else {
>> set nr_regs 32
>> +} else {
>> + set nr_regs 8
>> }
>>
>> for { set r 0 } { $r < $nr_regs } { incr r } {
>> --
>> 2.19.0
>
> With your patch, the test only fails for zmm registers due to broken
> XSAVE
> handling. This is fixed by Jan's patch. With both patches together,
> the test
> passes for -m32.
Thanks a lot, I pushed it!
Simon
prev parent reply other threads:[~2018-10-01 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 20:41 Simon Marchi
2018-10-01 9:49 ` Metzger, Markus T
2018-10-01 16:04 ` 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=109ef268e8076ad4b46fd6bb0b793432@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=simon.marchi@ericsson.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