From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gingold@adacore.com, stan@codesourcery.com,
mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v2 - part 0)
Date: Fri, 14 Nov 2008 17:04:00 -0000 [thread overview]
Message-ID: <uhc6anx2p.fsf@gnu.org> (raw)
In-Reply-To: <491D93D8.6060007@codesourcery.com>
> Date: Fri, 14 Nov 2008 07:06:00 -0800
> From: Stan Shebs <stan@codesourcery.com>
> CC: Stan Shebs <stan@codesourcery.com>, Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
>
> > # of expected passes 4299
> > # of unexpected failures 3107
> Hmmm, that's kind of high, even for an initial port. Is it mainly that
> shared library bits are missing, or something else?
>
> My natural inclination is to accept the code into the trunk after review
> - I suspect that the next round of changes will be more invasive into
> the rest of GDB, and it would be easier to consider each of those
> separately from the basic port. But, I have a track record of being too
> optimistic on this strategy, ahem. :-) What do other people think?
I'd like to know whether there are any large sets of failed tests that
have something in common (a.k.a. unsupported GDB features), before I
make up my mind.
next prev parent reply other threads:[~2008-11-14 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 10:14 Tristan Gingold
2008-11-13 15:11 ` Tristan Gingold
2008-11-13 19:41 ` Mark Kettenis
2008-11-13 20:40 ` Tristan Gingold
2008-11-13 21:41 ` Stan Shebs
2008-11-14 16:28 ` Tristan Gingold
2008-11-14 16:41 ` Stan Shebs
2008-11-14 17:04 ` Eli Zaretskii [this message]
2008-11-14 17:44 ` Tristan Gingold
2008-11-14 17:40 ` Joel Brobecker
2008-11-14 17:47 ` Mark Kettenis
2008-11-14 15:51 ` Eli Zaretskii
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=uhc6anx2p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=mark.kettenis@xs4all.nl \
--cc=stan@codesourcery.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