Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com, gdb-testers@sources.redhat.com
Subject: Re: First release candidate for GDB 6.4 available
Date: Tue, 22 Nov 2005 14:09:00 -0000	[thread overview]
Message-ID: <20051122140935.GC15501@nevyn.them.org> (raw)
In-Reply-To: <20051122083855.GH1635@adacore.com>

On Tue, Nov 22, 2005 at 12:38:55AM -0800, Joel Brobecker wrote:
> Hello,
> 
> This is to announce that the first release candidate is now available
> for download at:
> 
>         ftp://sources.redhat.com/pub/gdb/snapshots/branch/gdb-6.3.90.tar.bz2
>         ftp://sources.redhat.com/pub/gdb/snapshots/branch/gdb-6.3.90.tar.gz
> 
> I will run a quick build & test of this tarball on the following
> platforms: alpha-tru64 5.1b, ia64-linux, mips-irix, ppc-aix,
> x86-solaris, x86_64-linux, sparc-solaris.
> 
> There should be no surprise there as I have been doing nightly builds
> off the branch since it was created and didn't receive any build
> breakage incident.
> 
> If you have access to other platforms and would like to report their
> status, that would be very helpful.

These are from a slightly patched GDB (Debian's), using the 20051119
snapshot, but may be useful anyway.  All are for GNU/Linux native.

i486:

                === gdb Summary ===

# of expected passes            10837
# of unexpected failures        40
# of unexpected successes       1
# of expected failures          42
# of known failures             42
# of untested testcases         2
# of unsupported tests          8

S/390:

		=== gdb Summary ===

# of expected passes		10798
# of unexpected failures	30
# of expected failures		42
# of known failures		33
# of untested testcases		2
# of unsupported tests		10

IA64:

		=== gdb Summary ===

# of expected passes		10604
# of unexpected failures	99
# of unexpected successes	2
# of expected failures		42
# of known failures		34
# of unresolved testcases	9
# of untested testcases		2
# of unsupported tests		11

Alpha:

		=== gdb Summary ===

# of expected passes		10512
# of unexpected failures	127
# of unexpected successes	2
# of expected failures		37
# of known failures		33
# of untested testcases		3
# of unsupported tests		11

PowerPC:

		=== gdb Summary ===

# of expected passes		10965
# of unexpected failures	81
# of expected failures		42
# of known failures		35
# of unresolved testcases	2
# of untested testcases		2
# of unsupported tests		10

SPARC:

	=== gdb Summary ===

# of expected passes		10504
# of unexpected failures	253
# of expected failures		42
# of known failures		36
# of unresolved testcases	17
# of untested testcases		2
# of unsupported tests		10

Built OK, but testsuite disabled for other reasons: mips, mipsel, arm,
m68k.

Of all of Debian's architctures, none failed to build (which may be a
first for a snapshot).  HPPA hasn't tried yet but Randolph's been
active lately so I presume it will work when the build daemon is
available.  SPARC is in the worst shape, followed by Alpha, which is
pretty typical.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-11-22 14:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22  8:39 Joel Brobecker
2005-11-22 14:09 ` Daniel Jacobowitz [this message]
2005-11-25  5:28   ` Randolph Chung
2005-11-22 23:16 ` Ulrich Weigand
2005-11-22 23:20 ` info types question Stefan Burström
2005-11-22 23:45   ` Daniel Jacobowitz
2005-11-22 23:50     ` Stefan Burström
2005-11-25  3:09       ` Daniel Jacobowitz
2005-11-22 23:20 ` First release candidate for GDB 6.4 available Mark Kettenis
2005-11-23  5:17 ` Wu Zhou
2005-11-25  2:47   ` Mark Kettenis
2005-11-25  2:51     ` Wu Zhou
2005-11-25  3:15       ` Daniel Jacobowitz
2005-11-25  4:21         ` Wu Zhou
2005-11-25 15:57           ` Kunal Parmar
2005-11-28 22:44 ` Mark Kettenis
2005-11-23 19:34 Newman, Sarah R

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=20051122140935.GC15501@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-testers@sources.redhat.com \
    --cc=gdb@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