From: Jim Wilson <jimw@sifive.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: jiangshuai_li@c-sky.com,
"Andrew Burgess" <andrew.burgess@embecosm.com>,
guoren@kernel.org, gdb-patches@sourceware.org,
夏立方 <lifang_xia@c-sky.com>, yunhai_shang <yunhai_shang@c-sky.com>
Subject: Re: [PATCH] riscv: add gdbserver support
Date: Tue, 21 Jan 2020 23:56:00 -0000 [thread overview]
Message-ID: <CAFyWVaaRaG0JNpkMCmSTMAhpe1WbMV7zKB3knfpp9yivrjzpgg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2001202307240.15714@redsun52.ssa.fujisawa.hgst.com>
On Mon, Jan 20, 2020 at 3:33 PM Maciej W. Rozycki <macro@wdc.com> wrote:
> NB my RV64 HiFive Unleashed test results look like below:
For my last run in early January, on fedora rawhide with a patched
4.15 linux kernel and lots of packages installed, I get
=== gdb Summary ===
# of expected passes 62674
# of unexpected failures 980
# of unexpected successes 2
# of expected failures 71
# of unknown successes 5
# of known failures 105
# of untested testcases 93
# of unresolved testcases 10
# of unsupported tests 243
So it looks similarly to your results.
Jim
next prev parent reply other threads:[~2020-01-21 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 5:01 jiangshuai_li
2020-01-20 23:33 ` Jim Wilson
2020-01-21 0:30 ` Maciej W. Rozycki
2020-01-21 2:13 ` Simon Marchi
2020-01-21 2:17 ` Maciej W. Rozycki
2020-01-21 13:01 ` Andrew Burgess
2020-01-21 13:28 ` Andrew Burgess
2020-01-21 13:47 ` Andreas Schwab
2020-01-22 0:11 ` Jim Wilson
2020-01-22 0:45 ` Jim Wilson
2020-01-22 10:19 ` Jim Wilson
2020-01-22 14:08 ` Andrew Burgess
2020-01-21 23:56 ` Jim Wilson [this message]
2020-01-22 5:26 ` Guo Ren
2020-01-22 6:15 ` Jim Wilson
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=CAFyWVaaRaG0JNpkMCmSTMAhpe1WbMV7zKB3knfpp9yivrjzpgg@mail.gmail.com \
--to=jimw@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=guoren@kernel.org \
--cc=jiangshuai_li@c-sky.com \
--cc=lifang_xia@c-sky.com \
--cc=macro@wdc.com \
--cc=yunhai_shang@c-sky.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