Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] gdb.c++/method.exp: xfail for missing const
Date: Mon, 08 Apr 2002 11:46:00 -0000	[thread overview]
Message-ID: <20020408144603.B495@nevyn.them.org> (raw)
In-Reply-To: <200204081832.g38IWFf11265@duracef.shout.net>

On Mon, Apr 08, 2002 at 01:32:15PM -0500, Michael Elizabeth Chastain wrote:
> How about this for printing "this" in a const method?
> 
> It reports PASS if the required "const" is present.
> It reports (XFAIL|FAIL) with "missing const" if required "const" is missing.
>   XFAIL if stabs debugging format
>   FAIL  if any other debugging format
> It reports FAIL for any other output.

I would rather do it based on compiler version:

> It reports PASS if the required "const" is present.
    [I'll accept this.  It could be an XPASS/KPASS if something really
     bizarre happened and we started ADDING consts.  But that'd be
     caught elsewhere, so let's not worry about it.]

> It reports (XFAIL|FAIL) with "missing const" if required "const" is missing.
>   XFAIL if stabs debugging format

     I would prefer:
       "XFAIL if stabs debugging format and GCC and GCC version < 3.1"
     so that we go to FAIL instead of XFAIL if the stabs const code stops
     working in either GCC or GDB.

>   FAIL  if any other debugging format
> It reports FAIL for any other output.

Great otherwise.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-04-08 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 11:32 Michael Elizabeth Chastain
2002-04-08 11:46 ` Daniel Jacobowitz [this message]
2002-04-08 12:28 Michael Elizabeth Chastain
2002-04-08 14:07 ` Daniel Jacobowitz
2002-04-08 15:24 Michael Elizabeth Chastain

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=20020408144603.B495@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.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