public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: zengxiao@eswincomputing.com
To: gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, andrew@sifive.com, shihua@iscas.ac.cn,
	zengxiao <zengxiao@eswincomputing.com>
Subject: [PATCH,V1 0/1] RISC-V: Make R_RISCV_SUB6 conforms to riscv abi standard
Date: Tue, 15 Nov 2022 14:51:58 +0800	[thread overview]
Message-ID: <20221115065159.2353620-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 +++++
 .../testsuite/binutils-all/riscv/dwarf-SUB6.d | 31 +++++++++++++++++++
 .../testsuite/binutils-all/riscv/dwarf-SUB6.s | 12 +++++++
 3 files changed, 50 insertions(+)
 create mode 100644 binutils/testsuite/binutils-all/riscv/dwarf-SUB6.d
 create mode 100644 binutils/testsuite/binutils-all/riscv/dwarf-SUB6.s

-- 
2.34.1


             reply	other threads:[~2022-11-15  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  6:51 zengxiao [this message]
2022-11-15  6:51 ` [PATCH,V1 1/1] " zengxiao
  -- strict thread matches above, loose matches on Subject: below --
2022-11-15  8:09 [PATCH,V1 0/1] " zengxiao
2022-11-15  6:46 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=20221115065159.2353620-1-zengxiao@eswincomputing.com \
    --to=zengxiao@eswincomputing.com \
    --cc=andrew@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kito.cheng@gmail.com \
    --cc=shihua@iscas.ac.cn \
    /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).