public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tromey@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: [pushed] Invert test in gdb.ada/ptype_tagged_param.exp
Date: Mon, 30 Jan 2023 08:03:16 -0700	[thread overview]
Message-ID: <87v8konjyj.fsf@tromey.com> (raw)
In-Reply-To: <af6eaddb-e0cd-4988-0e97-706f18b70ebc@palves.net> (Pedro Alves's message of "Fri, 27 Jan 2023 21:11:41 +0000")

>>>> kfail "no debug info" $gdb_test_name
>> 
Pedro> Why is this a kfail instead of an xfail?  Is there really a GDB bug here?
>> 
>> It's just my perennial inability to distinguish the two.  There's no gdb
>> bug, this seems to be a compiler issue.  If changing it to xfail is
>> correct, let me know and I will do it.  

Pedro> :-)

Pedro> Yes, kfail is correct.

Confusing!  But I think just a typo.
I'm going to send a patch to change it.

Tom

  reply	other threads:[~2023-01-30 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 17:24 Tom Tromey
2023-01-27 20:15 ` Pedro Alves
2023-01-27 21:01   ` Tom Tromey
2023-01-27 21:11     ` Pedro Alves
2023-01-30 15:03       ` Tom Tromey [this message]
2023-01-30 15:22         ` Pedro Alves

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=87v8konjyj.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).