From: Mark Wielaard <mark@klomp.org>
To: Andreas Schwab <schwab@suse.de>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] backends: add abi_cfi and register_info callbacks for RISC-V
Date: Thu, 14 Jun 2018 23:28:00 -0000 [thread overview]
Message-ID: <20180614232812.GG7539@wildebeest.org> (raw)
In-Reply-To: <mvm602ndlqn.fsf@suse.de>
On Wed, Jun 13, 2018 at 12:28:00PM +0200, Andreas Schwab wrote:
> From
> <https://github.com/riscv/riscv-isa-manual/raw/master/release/riscv-spec-v2.2.pdf>
> and GCC source.
This looks good as far as I can see.
How does the result of make check look now on a native riscv system?
Could you provide a testcase for tests/run-allregs.sn and/or
tests/run-addrcfi.sh if possible so people can check things work on
other arches?
If this is enough to actually unwind could you look at providing an
tests/run-backtrace-core-riscv.sh testcase (the existing ones should
explain how to generate the (static) executable and core file for the
test, but if it is unclear please ask.
Thanks,
Mark
next prev parent reply other threads:[~2018-06-14 23:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 10:28 Andreas Schwab
2018-06-14 23:28 ` Mark Wielaard [this message]
2018-06-18 8:01 ` Andreas Schwab
2018-06-20 11:16 ` Mark Wielaard
2018-06-20 12:38 ` Andreas Schwab
2018-06-20 12:59 ` Mark Wielaard
2018-06-20 13:55 ` Andreas Schwab
2018-06-20 20:49 ` Mark Wielaard
2018-07-11 13:40 ` Andreas Schwab
2018-07-24 14:13 ` Andreas Schwab
2018-07-26 16:03 ` Mark Wielaard
2018-10-02 12:46 ` [PATCH] Handle ADD/SUB relocations Andreas Schwab
2018-10-13 21:23 ` Mark Wielaard
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=20180614232812.GG7539@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=schwab@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).