From: Kito Cheng <kito.cheng@gmail.com>
To: umesh kalappa <ukalappa@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: RISCV relocs .
Date: Fri, 27 May 2022 17:45:36 +0800 [thread overview]
Message-ID: <CA+yXCZDyxqZMwt7roHkAfrmJyZUc3=SitSrLG3+OdDY1iUzfOA@mail.gmail.com> (raw)
In-Reply-To: <CAKfPWSki1-3Jb5fd+NWOczvbeyaF1zRCuSrc874vzNOcSSTSRw@mail.gmail.com>
Those relocations are used in EH frame and debug info IIRC.
On Fri, May 27, 2022 at 5:31 PM umesh kalappa via Binutils
<binutils@sourceware.org> wrote:
>
> Hi All ,
>
> We build the loadable kernel module ,where we do partially link (-r) and
> for riscv
>
> we are understanding the relocs like
>
> 000000000030 001300000034 R_RISCV_SUB6 0000000000000002 <null> + 0
> 000000000033 001700000035 R_RISCV_SET6 0000000000000008 <null> + 0
>
> Currently we are ignoring the above relocs ,is that ok to do so ?
>
> ~Umesh
next prev parent reply other threads:[~2022-05-27 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 9:30 umesh kalappa
2022-05-27 9:45 ` Kito Cheng [this message]
2022-05-27 10:07 ` umesh kalappa
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='CA+yXCZDyxqZMwt7roHkAfrmJyZUc3=SitSrLG3+OdDY1iUzfOA@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=binutils@sourceware.org \
--cc=ukalappa@gmail.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).