From: "mark at klomp dot org" <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: Sat, 02 Nov 2024 19:03:25 +0000 [thread overview]
Message-ID: <bug-31653-13298-Wv8BjzPa9V@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 #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to laokz from comment #2)
> When compiled the tests, we added -O2 option. Without -O2, all tests passed
> and no R_RISCV_SET/SUB_ULEB128 generated. It seems that gcc/binutils do
> support generating these relocs but readelf doesn't support applying them
> yet.
How exactly do you add the -O2 option?
> Reproduce steps:
> 0. platform: openSUSE Tumbleweed 20241029 - Kernel 6.11.5-1-default, riscv
> qemu vm, gcc-14.2.1, binutils-2.43.1.20240828-2
> 1. echo "int main(){}" >z.c
> 2. gcc -g -O2 z.c
plus -c
> 3. readelf -Wr z.o|grep 128
So this "reproduces" the warnings.
But I cannot replicate using the debugedit build/tests.
Is there a special way you are configuring/building and/or running make check?
If you are editing debugedit.at to explicitly add -O2 then please just don't do
that.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-11-02 19:03 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 [this message]
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
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-Wv8BjzPa9V@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).