Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: David Blaikie <dblaikie@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patch] [gdb/testsuite] XFAIL under Clang tests using label debug info
Date: Thu, 24 Apr 2014 10:42:00 -0000	[thread overview]
Message-ID: <5358EA8F.3000601@redhat.com> (raw)
In-Reply-To: <CAENS6EtFF4hPJe3uqJBkPf4q8c0n4RvV1_jO=6mWWEp=X2HbnA@mail.gmail.com>

Hi David,

On 04/14/2014 12:25 AM, David Blaikie wrote:
>  
> +if {[test_compiler_info {clang-*-*}]} {  setup_xfail clang/14500 *-*-* }
>  gdb_test "break here" \
>    "Breakpoint.*at.*" \
>    "breakpoint here"
>  
> +if {[test_compiler_info {clang-*-*}]} {  setup_xfail clang/14500 *-*-* }

A suggestion -- in these cases where we have a bunch of similar
setup_xfails for a single bug, it's good to do as e.g.,
gdb.cp/temargs.exp does.  That is, something like

set have_clang_14500_bug [test_compiler_info {clang-*-*}]

# Short description of bug here.
proc setup_xfail_clang_14500 {} {
  global have_clang_14500_bug

  if { $have_clang_14500_bug } {
     setup_xfail clang/14500 *-*-*
  }
}

And then:

+ setup_xfail_clang_14500
 gdb_test "break main:there" \
   "Breakpoint.*at.*" \
   "breakpoint there"

etc.

A style like that adds less clutter, and, is less typo prone than:

> +if {[test_compiler_info {clang-*-*}]} {  setup_xfail clang/14500 *-*-* }

all over.  And it's a single place to change the condition to be
dependent on clang version, in the future, if you want to.

-- 
Pedro Alves


      parent reply	other threads:[~2014-04-24 10:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 23:26 David Blaikie
2014-04-23 22:03 ` Doug Evans
2014-04-25  3:23   ` David Blaikie
2019-09-05 22:12     ` David Blaikie
2019-09-06  2:48       ` Christian Biesinger via gdb-patches
2019-09-06  4:17         ` Eric Christopher
2019-09-06 17:26           ` Christian Biesinger via gdb-patches
2019-09-06 20:23             ` David Blaikie
2019-09-06 20:25               ` Christian Biesinger via gdb-patches
     [not found]       ` <CADPb22Svrkdy6eOmcY2CxYAHfmaz_vRPE8sLDrujJCjbXCFMNg@mail.gmail.com>
2019-09-06 21:19         ` David Blaikie
2014-04-24 10:42 ` Pedro Alves [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=5358EA8F.3000601@redhat.com \
    --to=palves@redhat.com \
    --cc=dblaikie@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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