From: zengxiao@eswincomputing.com
To: binutils@sourceware.org
Cc: zhengyu@eswincomputing.com, jinyanjiang@eswincomputing.com,
cri-sw-toolchain@eswincomputing.com,
zengxiao <zengxiao@eswincomputing.com>
Subject: [PATCH 0/1] RISC-V: Make R_RISCV_SUB6 conforms to riscv abi standard
Date: Fri, 14 Oct 2022 14:35:19 +0800 [thread overview]
Message-ID: <20221014063520.1428330-1-zengxiao@eswincomputing.com> (raw)
From: zengxiao <zengxiao@eswincomputing.com>
Hi all RISC-V folks:
When riscv-objdump is used to generate dwarf information, problems are found, like:
DW_CFA_??? (User defined call frame op: 0x3c)
This error is related to that riscv-objdump does not follow the riscv R_RISCV_SUB6 standard.
Riscv-readelf is correct because it follows the R_RISCV_SUB6 standard.
There are test cases in https://github.com/zeng-xiao/gnu-bug-fix/tree/main/EG-769
that describe the error in detail.
---
zengxiao (1):
RISC-V: Make R_RISCV_SUB6 conforms to riscv abi standard
bfd/elfxx-riscv.c | 7 +++++++
1 file changed, 7 insertions(+)
--
2.34.1
next reply other threads:[~2022-10-14 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 6:35 zengxiao [this message]
2022-10-14 6:35 ` [PATCH 1/1] " zengxiao
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=20221014063520.1428330-1-zengxiao@eswincomputing.com \
--to=zengxiao@eswincomputing.com \
--cc=binutils@sourceware.org \
--cc=cri-sw-toolchain@eswincomputing.com \
--cc=jinyanjiang@eswincomputing.com \
--cc=zhengyu@eswincomputing.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).