From: "laokz at foxmail dot com" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/31653] RISC-V: readelf fails to apply R_RISCV_SET/SUB_ULEB128 relocations: [debugedit 5.0] testsuite: 10 11 19 23 failed
Date: Mon, 04 Nov 2024 04:12:44 +0000 [thread overview]
Message-ID: <bug-31653-13298-3D4qhGkdZu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31653-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31653
--- Comment #6 from laokz <laokz at foxmail dot com> ---
(In reply to Mark Wielaard from comment #5)
> Created attachment 15777 [details]
> Ignore stderr in AT_CHECK for readelf stderr warnings
>
> Aha, OK now I understand how to replicate it.
> ./configure CC="gcc -O2 -g"
> Will do the same. Always run gcc with -O2 even in the testsuite.
>
> Even though I think you should not add extra compiler flags to the testsuite
> I see how if you do warnings from readelf would be an issue.
>
> Luckily it is easy to ignore stderr warnings with AT_CHECK.
> Could you try the attached patch?
Yes. I tried and it worked! (rebased against our debugedit-5.0 package)
> If there is no bug yet, we should file a binutils bug against readelf
> (apply_relocations) should handle R_RISCV_SET_ULEB128 and R_RISCV_SUB_ULEB128
Indeed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-11-04 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 8:35 [Bug debugedit/31653] New: " akyragvtdizi at gmail dot com
2024-05-15 11:25 ` [Bug debugedit/31653] " mark at klomp dot org
2024-10-30 13:10 ` laokz at foxmail dot com
2024-11-02 19:03 ` mark at klomp dot org
2024-11-03 3:01 ` laokz at foxmail dot com
2024-11-03 16:47 ` mark at klomp dot org
2024-11-04 4:12 ` laokz at foxmail dot com [this message]
2024-11-05 23:46 ` mark at klomp dot org
2024-11-05 23:46 ` 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-3D4qhGkdZu@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).