Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Alan Hayward <Alan.Hayward@arm.com>,
	Simon Marchi <simon.marchi@polymtl.ca>,
	Andrew Burgess <andrew.burgess@embecosm.com>,
	"gdb-patches\\@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: Change in binutils-gdb[master]: [gdb/tdep] Fix 'Unexpected register class' assert in amd64_push_argum...
Date: Wed, 16 Oct 2019 14:21:00 -0000	[thread overview]
Message-ID: <736be29d-18d7-af6e-f0fb-538f8499df47@suse.de> (raw)
In-Reply-To: <CA883C0B-077D-409C-AB54-C6C5FB9BB309@arm.com>

On 16-10-2019 13:08, Alan Hayward wrote:
>> On 15 Oct 2019, at 18:23, Alan Hayward <Alan.Hayward@arm.com> wrote:
>>
>>
>>
>>> On 15 Oct 2019, at 09:04, Tom de Vries (Code Review) <gerrit@gnutoolchain-gerrit.osci.io> wrote:
>>>
>>> Tom de Vries has posted comments on this change.
>>>
>>> Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/30
>>> ......................................................................
>>>
>>>
>>> Patch Set 1:
>>>
>>> https://sourceware.org/ml/gdb-patches/2019-10/msg00343.html:
>>> ...
>>> On 14-10-2019 15:10, Alan Hayward wrote:
>>>>> This exposes 9 more FAILs of the PR tdep/25096 type, so mark all 12 of them as
>>>>> KFAIL.
>>>> When I run the test, I get three unexpected passes:
>>>>
>>>>
>>>> # of expected passes		9388
>>>> # of unknown successes		3
>>>> # of known failures		9
>>>>
>>>> KPASS: gdb.base/infcall-nested-structs.exp: l=c++: types-tc-tf: p/d check_arg_struct_02_01 (ref_val_struct_02_01) (PRMS gdb/25096)
>>>> KPASS: gdb.base/infcall-nested-structs.exp: l=c++: types-ts-tf: p/d check_arg_struct_02_01 (ref_val_struct_02_01) (PRMS gdb/25096)
>>>> KPASS: gdb.base/infcall-nested-structs.exp: l=c++: types-ti-tf: p/d check_arg_struct_02_01 (ref_val_struct_02_01) (PRMS gdb/25096)
>>>
>>> That could be due to registers happening to have the correct value.
>>>
>>> Do these turn into KFAILs if you add:
>>> ...
>>> diff --git a/gdb/testsuite/gdb.base/infcall-nested-structs.exp
>>> b/gdb/testsuite/gdb.base/infcall-nested-structs.
>>> exp
>>> index 957eb31bdc2..f62f636aa11 100644
>>> --- a/gdb/testsuite/gdb.base/infcall-nested-structs.exp
>>> +++ b/gdb/testsuite/gdb.base/infcall-nested-structs.exp
>>> @@ -134,6 +134,7 @@ proc run_tests { lang types } {
>>>
>>>    if { $lang == "c++" && $name == "struct_02_01"
>>>         && [regexp "^types-(tf-t(c|s|i)|t(c|s|i)-tf)" $types match] } {
>>> +           gdb_test_no_output "set \$xmm0.v2_int64\[0\] = 0"
>>>        setup_kfail gdb/25096 "x86_64-*-linux*"
>>>    }
>>>    gdb_test "p/d check_arg_${name} (ref_val_${name})" "= 1"
>>> ...
>>> ?
>>> ...
>>
>> I still get KPASSes with that change.
>> Also tried adding the line to the next block in the test with the same if statements, but it didn’t help.
>>
>>
> 
> Sorry, ignore my comment.
> I was accidentally running using the 8.3 branch.
> When I use the latest master, it all works for me.
> 

Thanks, that explains it for me.  The three KPASSES is what you see when
you apply the patch to a version that does not contain the commit
6dfc0041129 "gdb/testsuite: Fix typos in infcall-nested-structs.c".

Thanks,
- Tom


  reply	other threads:[~2019-10-16 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5A0DCAF8-4BFF-49C2-86C7-5E9C5B5A911B@arm.com>
2019-10-15 17:23 ` Fwd: " Alan Hayward
2019-10-16 11:09   ` Alan Hayward
2019-10-16 14:21     ` Tom de Vries [this message]
     [not found] <gerrit.1571043259000.I8b66345bbf5c00209ca75b1209fd4d60b36e9ede@gnutoolchain-gerrit.osci.io>
2019-10-15  4:13 ` Simon Marchi (Code Review)
2019-10-15  8:04 ` Tom de Vries (Code Review)

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=736be29d-18d7-af6e-f0fb-538f8499df47@suse.de \
    --to=tdevries@suse.de \
    --cc=Alan.Hayward@arm.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=simon.marchi@polymtl.ca \
    /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