From: Stan Shebs <stan@codesourcery.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Stan Shebs <stan@codesourcery.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v2 - part 0)
Date: Fri, 14 Nov 2008 16:41:00 -0000 [thread overview]
Message-ID: <491D93D8.6060007@codesourcery.com> (raw)
In-Reply-To: <2C387CFB-1541-41B5-964C-68692E078BFA@adacore.com>
Tristan Gingold wrote:
>
> On Nov 13, 2008, at 7:03 PM, Stan Shebs wrote:
>> Anyway, I'm the most logical reviewer for the bulk of native support,
>> I'll give you some feedback in the next few days. In the meantime,
>> please run the testsuite, let's see what the basic numbers are
>> looking like.
>
> Thanks. I plan to post a new version of the patches that addresses
> Eli's review.
>
> Here is the first testsuite result:
>
> === gdb Summary ===
>
> # 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?
Stan
next prev parent reply other threads:[~2008-11-14 15:06 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 [this message]
2008-11-14 17:04 ` Eli Zaretskii
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=491D93D8.6060007@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=mark.kettenis@xs4all.nl \
/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