From: Vineet Gupta via Libc-alpha <libc-alpha@sourceware.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Shahab Vahedi <Shahab.Vahedi@synopsys.com>,
libc-alpha@sourceware.org
Cc: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH v2] ARC: update definitions in elf/elf.h
Date: Tue, 22 Nov 2022 20:13:46 -0800 [thread overview]
Message-ID: <1eb9f4ab-6289-0e0d-a488-4e17994b13ba@linux.dev> (raw)
In-Reply-To: <facdfda0-cb2b-da24-1239-0b990a0328a9@linaro.org>
On 11/21/22 06:30, Adhemerval Zanella Netto wrote:
> On 21/11/22 10:06, Shahab Vahedi via Libc-alpha wrote:
>> While porting ARCv2 to elfutils [1], it was brought up that the
>> necessary changes to the project's libelf/elf.h must come from
>> glibc, because they sync it from glibc [2]. Therefore, this patch
>> is to update ARC entries in elf/elf.h.
>>
>> The majority of the update is about adding new definitions,
>> specially for the relocations. However, there is one rename, one
>> deletion, and one change:
>>
>> - R_ARC_JUMP_SLOT renamed to R_ARC_JMP_SLOT to match binutils.
>> - R_ARC_B26 removed because it is unused and deprecated.
>> - R_ARC_TLS_DTPOFF_S9 changed from 0x4a to the correct value 0x49.
>>
>> [1]
>> https://sourceware.org/pipermail/elfutils-devel/2022q4/005530.html
>>
>> [2]
>> https://sourceware.org/pipermail/elfutils-devel/2022q4/005548.html
>>
>> Signed-off-by: Shahab Vahedi<shahab@synopsys.com>
> We discussed this briefly on glibc patchwork review meeting [1],
> and if does not trigger any regression it ok to arch maintainers
> to handle such changes.
Shahab as a process followup, can you run the full glibc testsuite w/
and w/o this change and post the results summary here. It should be easy
to do this with hsdk dev board. It can also help find fill the the glibc
testing log for arc for the upcoming release ;-) as 2.36 [1] seems untested.
-Vineet
[1] https://sourceware.org/glibc/wiki/Release/2.36
next prev parent reply other threads:[~2022-11-23 4:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 13:15 [PATCH] ARC: update definitions in elf/elf.h Shahab Vahedi via Libc-alpha
2022-11-19 0:34 ` Vineet Gupta via Libc-alpha
2022-11-21 13:07 ` Shahab Vahedi via Libc-alpha
2022-11-21 13:06 ` [PATCH v2] " Shahab Vahedi via Libc-alpha
2022-11-21 14:30 ` Adhemerval Zanella Netto via Libc-alpha
2022-11-23 4:13 ` Vineet Gupta via Libc-alpha [this message]
2022-11-27 17:38 ` [PATCH v3 0/2] Update ARC " Shahab Vahedi via Libc-alpha
2022-11-27 17:38 ` [PATCH v3 1/2] scripts: Add "|" operator support to glibcpp's parsing Shahab Vahedi via Libc-alpha
2022-11-27 18:21 ` Florian Weimer via Libc-alpha
2022-11-30 2:11 ` Vineet Gupta via Libc-alpha
2022-11-27 17:38 ` [PATCH v3 2/2] ARC: update definitions in elf/elf.h Shahab Vahedi via Libc-alpha
2022-11-30 2:11 ` Vineet Gupta via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1eb9f4ab-6289-0e0d-a488-4e17994b13ba@linux.dev \
--to=libc-alpha@sourceware.org \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Shahab.Vahedi@synopsys.com \
--cc=adhemerval.zanella@linaro.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vineet.gupta@linux.dev \
/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).