Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason R Thorpe <thorpej@wasabisystems.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Get Alpha target to GDB_MULTI_ARCH_PARTIAL
Date: Sat, 20 Apr 2002 13:31:00 -0000	[thread overview]
Message-ID: <20020420133134.V1627@dr-evil.shagadelic.org> (raw)
In-Reply-To: <20020420095435.T1627@dr-evil.shagadelic.org>; from thorpej@wasabisystems.com on Sat, Apr 20, 2002 at 09:54:36AM -0700

On Sat, Apr 20, 2002 at 09:54:36AM -0700, Jason R Thorpe wrote:

 >                 === gdb Summary ===
 > 
 > # of expected passes            6595
 > # of unexpected failures        945
 > # of unexpected successes       4
 > # of expected failures          143
 > # of unresolved testcases       118
 > # of untested testcases         6
 > # of unsupported tests          3
 > 
 > I would really like to know what the test results are on Digital Unix
 > or Linux (I can't easily install either of those on any of my Alpha
 > systems, unfortunately).

FWIW, a very large number of my failures go away when I make sure the
testsuite uses gcc-current rather than the 2.95.3 that's currently shipped
with NetBSD.  (Lots of the failures are off-by-one in line numbers.)

Is there a way besides placing the location of the alternate compiler
first in the PATH to make sure the correct compiler is chosen?

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>


  reply	other threads:[~2002-04-20 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  9:54 Jason R Thorpe
2002-04-20 13:31 ` Jason R Thorpe [this message]
2002-04-20 13:37   ` Daniel Jacobowitz
2002-04-23 11:45   ` Michael Snyder
2002-04-20 17:10 ` Jason R Thorpe
2002-04-20 22:38 ` Andrew Cagney
2002-04-22  6:32   ` Joel Brobecker
2002-04-20 22:48 ` Andrew Cagney
2002-04-20 22:51 ` Andrew Cagney
2002-04-23 11:49 ` Michael Snyder

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=20020420133134.V1627@dr-evil.shagadelic.org \
    --to=thorpej@wasabisystems.com \
    --cc=gdb-patches@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