public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
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: Wed, 20 Jun 2018 20:49:00 -0000	[thread overview]
Message-ID: <1529527688.12946.141.camel@klomp.org> (raw)
In-Reply-To: <mvmbmc5lfz8.fsf@suse.de>

On Wed, 2018-06-20 at 15:55 +0200, Andreas Schwab wrote:
> It's probably because there are more than just simple relocations on
> debug sections, more than reloc_simple_type can handle.

aha, ok, but it looks like RISCV_(ADD|SUB)(8|16|32|64) should not be
too hard to handle. The other ones (RISCV_SETX) might be a little
harder. They are not used much though and only against .debug_frame. So
if you get RISC_ADD/SUB going that probably handles most uses. Maybe
backend reloc_simple_type hook needs to be changed a bit to handle
them. But that shouldn't really be a problem, all callers are internal
(libdwfl/relocate.c and strip.c).

Cheers,

Mark

  reply	other threads:[~2018-06-20 20:49 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
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 [this message]
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=1529527688.12946.141.camel@klomp.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).