From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] gdb.c++/method.exp: xfail for missing const
Date: Mon, 08 Apr 2002 12:28:00 -0000 [thread overview]
Message-ID: <200204081928.g38JS9A18557@duracef.shout.net> (raw)
Daniel Jacobowitz writes:
> [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.]
I don't follow you. Do you mean "print this" in a non-const method that
replies "const A *" or "const A * const"? That's already a straight FAIL.
> 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.
I would like that too. But how can the test script determine the gcc
version? I don't see a way to do this in gdb/lib.exp.
BTW I'll add a section for "const class {...} *" specifically so that
we can kfail it eventually.
Michael C
next reply other threads:[~2002-04-08 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 12:28 Michael Elizabeth Chastain [this message]
2002-04-08 14:07 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 15:24 Michael Elizabeth Chastain
2002-04-08 11:32 Michael Elizabeth Chastain
2002-04-08 11:46 ` Daniel Jacobowitz
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=200204081928.g38JS9A18557@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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