From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Reanimate XStormy16
Date: Fri, 24 Sep 2004 18:13:00 -0000 [thread overview]
Message-ID: <415463CA.nail1EK119SUA@mindspring.com> (raw)
In-Reply-To: <20040924073720.GQ12802@cygbert.vinschen.de>
Corinna Vinschen <vinschen@redhat.com> wrote:
> Please note that XStormy16 is a very tiny 16 bit target. No signal
> support, no core file support, no shared libs, no libstdc++-v3,
> no threads.
Ah, okay. The number of UNSUPPORTED makes sense then.
The test suite is doing its job!
The ERROR and WARNING shouldn't be there. That looks like bugs
in the test suite.
> See the below list. If you're interested in more details, I can
> send you the gdb.log file.
Actually, could you do this:
grep -v '^PASS' gdb.sum
add a line saying which compiler version you tested with
mail it in to gdb-testers@
I'm trying to build gdb-testers@ as the home of "what versions of
gdb work and how well they work".
Michael
prev parent reply other threads:[~2004-09-24 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 17:02 Corinna Vinschen
2004-09-23 17:25 ` Michael Chastain
2004-09-24 7:36 ` Corinna Vinschen
2004-09-24 18:13 ` Michael Chastain [this message]
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=415463CA.nail1EK119SUA@mindspring.com \
--to=mec.gnu@mindspring.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