Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: Joel Brobecker <brobecker@adacore.com>,  gdb-patches@sources.redhat.com
Subject: Re: [hppa] FYI: confusion in unwind descriptor field meaning
Date: Sun, 13 Nov 2005 15:38:00 -0000	[thread overview]
Message-ID: <4375789C.2030809@tausq.org> (raw)
In-Reply-To: <8f2776cb0511112059u4c54acf1j13936c04fed3dbe6@mail.gmail.com>

> I don't know what state the test results from HPPA are in (please
> don't read any criticism in that), but I don't think we would need to
> tolerate any regressions from the change.  What's a real threat to
> progress is if there are so many variations we care about that it
> becomes difficult to test.

Test Run By tausq on Wed Nov  9 07:48:22 2005
Native configuration is hppa-unknown-linux-gnu

                === gdb Summary ===

# of expected passes            10813
# of unexpected failures        57
# of unexpected successes       1
# of expected failures          42
# of known failures             42
# of unresolved testcases       2
# of unsupported tests          3

HPUX is in much worse shape I'm afriad. I don't know the status of the
BSD port.

I believe we only have the following "actively" maintained configurations:

hppa-*-linux
hppa-*-openbsd
hppa-*-hpux*
hppa2.0w-*-hpux*
hppa64-*-hpux*

Which is still a lot, but not unmanagable yet. I somewhat actively
maintain and test the Linux port, and I can test the HPUX
configurations. I know nothing about BSD.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/


  reply	other threads:[~2005-11-12  5:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 23:55 Joel Brobecker
2005-11-10  1:27 ` Randolph Chung
2005-11-10  1:31   ` Joel Brobecker
2005-11-10  1:32     ` Randolph Chung
2005-11-10 19:18 ` Randolph Chung
2005-11-11 11:22   ` Joel Brobecker
2005-11-12  3:32     ` Randolph Chung
2005-11-12  4:22       ` Jim Blandy
2005-11-12  4:39         ` Jim Blandy
2005-11-12  4:59         ` Randolph Chung
2005-11-12  5:07           ` Jim Blandy
2005-11-12 13:21             ` Randolph Chung
2005-11-12 17:08               ` Jim Blandy
2005-11-13 15:38                 ` Randolph Chung [this message]
2005-11-13 18:27                   ` Daniel Jacobowitz
2005-11-19 19:15                     ` Randolph Chung
2005-11-13 18:23               ` Joel Brobecker
2005-11-13 18:28                 ` Daniel Jacobowitz
2005-11-13 18:36                   ` Joel Brobecker
2005-11-13 18:45                     ` Daniel Jacobowitz

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=4375789C.2030809@tausq.org \
    --to=randolph@tausq.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@red-bean.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