Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: aj@suse.de, mludvig@suse.cz, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/i386newframe] amd64newframe
Date: Mon, 19 May 2003 19:54:00 -0000	[thread overview]
Message-ID: <16073.14290.149959.474484@localhost.redhat.com> (raw)
In-Reply-To: <200305191715.h4JHFCei001220@elgar.kettenis.dyndns.org>

Mark Kettenis writes:
 > 
 > Yes, that would be great.  As soon as it performs better than the old
 > stuff, I'd like to move things over to mainline.
 > 
 > Mark


For me, I get:

63 failures in gdb.base
25 in gdb.c++
50 in gdb.threads
24 in gdb.mi
6 in gdb.asm

and

40 ERROR's

		=== gdb Summary ===

# of expected passes		8523
# of unexpected failures	177
# of unexpected successes	3
# of expected failures		46
# of known failures		19
# of unresolved testcases	38
# of unsupported tests		2


not perfect, but, I say, pretty close.

Hmm, I should run the testsuite for mainline too, doh.

elena



  reply	other threads:[~2003-05-19 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 18:34 Andreas Jaeger
2003-05-17 22:26 ` Mark Kettenis
2003-05-19  7:00   ` Michal Ludvig
2003-05-19  7:09     ` Andreas Jaeger
2003-05-19 17:15       ` Mark Kettenis
2003-05-19 19:54         ` Elena Zannoni [this message]
2003-05-19 22:31           ` Elena Zannoni
2003-05-20  5:49         ` Michal Ludvig
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17 15:19 Mark Kettenis
2003-05-19 15:31 ` Elena Zannoni
2003-05-19 17:11   ` Mark Kettenis
2003-05-19 21:24     ` Michal Ludvig
2003-05-19 21:40       ` Daniel Jacobowitz
2003-05-19 22:24       ` Elena Zannoni

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=16073.14290.149959.474484@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=aj@suse.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=mludvig@suse.cz \
    /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