From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite/cp] ctti.exp: partial overhaul
Date: Thu, 08 Jan 2004 04:23:00 -0000 [thread overview]
Message-ID: <20040108042301.76A614B35A@berman.michael-chastain.com> (raw)
> How about some KFAILs for GCC so I can see what I'm doing? :)
That would be good; the only problem is actually doing the work.
If I feed you a set of gdb.log files, can you file the necessary PR's
(if they aren't already filed) and feed me PR numbers? Or if you can't
do that, can you feed me URL's?
For your own purposes, you can grab the test and rip out one "continue"
in the middle. When all the results are PASS or KFAIL on all
configurations then I can rip out the "continue" for everybody.
The test script also does this to get to a defined place:
break main
run
next
next
next
next
next
next
Which is not really cool what with the freedom that compilers have to
choose line numbers. That's something else I have to fix up.
Michael C
next reply other threads:[~2004-01-08 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 4:23 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 2:12 Michael Elizabeth Chastain
2004-01-08 3:56 ` 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=20040108042301.76A614B35A@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=carlton@kealia.com \
--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