From: Andrew Cagney <ac131313@redhat.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: gdb@sources.redhat.com
Subject: Re: A few things we've been up to at Apple lately
Date: Sat, 09 Nov 2002 06:06:00 -0000 [thread overview]
Message-ID: <3DCD165D.4090009@redhat.com> (raw)
In-Reply-To: <20021109014927.A23527@molenda.com>
> Klee and I have been going over the testsuite on our platform for
> the past couple months. Over time, our gdb had diverged from the
> FSF gdb to the point where we had ~800 failures and a couple hundred
> unresolved test cases -- the testsuite was useless for us. We've
> been fixing testcases to match our output where we've purposely
> diverged from the FSF style; fixing our code to behave correctly;
> and filing Apple internal bug reports for all the known failures.
> We're down to 15-20 unfiled fails now, and many of those are known
> failures in the generic code.
Do you know about KFAIL?
(Thanks for the update).
Andrew
next prev parent reply other threads:[~2002-11-09 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 1:49 Jason Molenda
2002-11-09 6:06 ` Andrew Cagney [this message]
2002-11-09 12:12 ` Jason Molenda
2002-11-09 14:46 ` Daniel Jacobowitz
2002-11-09 14:52 ` Jason Molenda
2002-11-09 11:49 ` Klee Dienes
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=3DCD165D.4090009@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jason-swarelist@molenda.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