public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "akyragvtdizi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/31653] New: RISC-V: readelf fails to apply R_RISCV_SET/SUB_ULEB128 relocations: [debugedit 5.0] testsuite: 10 11 19 23 failed
Date: Thu, 18 Apr 2024 08:35:43 +0000	[thread overview]
Message-ID: <bug-31653-13298@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31653

            Bug ID: 31653
           Summary: RISC-V: readelf fails to apply R_RISCV_SET/SUB_ULEB128
                    relocations: [debugedit 5.0] testsuite: 10 11 19 23
                    failed
           Product: debugedit
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: debugedit
          Assignee: unassigned at sourceware dot org
          Reporter: akyragvtdizi at gmail dot com
                CC: debugedit at sourceware dot org
  Target Milestone: ---

Created attachment 15471
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15471&action=edit
testsuite log

While building debugedit-5.0 in a RISC-V nspawn environment, I encountered test
failures during the make check phase. Specifically, tests 10, 11, 19, and 23
failed due to unsupported relocation types as indicated by readelf warnings in
the logs. The exact messages are:

readelf: Warning: unable to apply unsupported reloc type 60 to section
.debug_loclists
readelf: Warning: unable to apply unsupported reloc type 61 to section
.debug_loclists

These warnings relate to relocation types 60 and 61, which correspond to
R_RISCV_SET_ULEB128 and R_RISCV_SUB_ULEB128, respectively. I am currently using
binutils version 2.42, and upon reviewing the readelf source code, it appears
that readelf may not yet support these RISC-V specific relocation types.

Given this issue, I propose temporarily skipping the affected tests (10, 11,
19, 23) for the RISC-V architecture to allow for successful test completions
while a solution is being developed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-04-18  8:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  8:35 akyragvtdizi at gmail dot com [this message]
2024-05-15 11:25 ` [Bug debugedit/31653] " mark at klomp dot org

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=bug-31653-13298@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=debugedit@sourceware.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).