From: Andreas Schwab <schwab@suse.de>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] backends: add abi_cfi and register_info callbacks for RISC-V
Date: Mon, 18 Jun 2018 08:01:00 -0000 [thread overview]
Message-ID: <mvmtvq0bk3v.fsf@suse.de> (raw)
In-Reply-To: <20180614232812.GG7539@wildebeest.org> (Mark Wielaard's message of "Fri, 15 Jun 2018 01:28:12 +0200")
On Jun 15 2018, Mark Wielaard <mark@klomp.org> wrote:
> How does the result of make check look now on a native riscv system?
FAIL: run-native-test.sh
return_value_location is missing
FAIL: run-low_high_pc.sh
lowpc: 220, highpc: 220lx
../../elfutils/src/size.c: [c84] 'handle_elf' highpc <= lowpc
lowpc: 41c, highpc: 41clx
../../elfutils/src/strip.c: [1c00] 'update_section_size' highpc <= lowpc
FAIL: run-backtrace-native.sh
FAIL: run-backtrace-dwarf.sh
FAIL: run-deleted.sh
set_initial_registers_tid is missing
FAIL: run-backtrace-native-core.sh
no corefile support
SKIP: run-backtrace-data.sh
no unwinding support
> 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.
I will work on these.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-06-18 8:01 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
2018-06-18 8:01 ` Andreas Schwab [this message]
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=mvmtvq0bk3v.fsf@suse.de \
--to=schwab@suse.de \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
/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).