From: Shahab Vahedi via Libc-alpha <libc-alpha@sourceware.org>
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
arcml <linux-snps-arc@lists.infradead.org>,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
Subject: Re: [PATCH] ARC: update definitions in elf/elf.h
Date: Mon, 21 Nov 2022 13:07:51 +0000 [thread overview]
Message-ID: <de0e7112-4f83-03b7-3dca-a132a59635c8@synopsys.com> (raw)
In-Reply-To: <abed8f65-738f-e9a4-7353-801ebc10fa70@linux.dev>
Hi Vineet,
FYI, a second version of the patch is submitted [1]. Regarding what
has changed, a changelog is put right after the sign-off line.
On 11/19/22 01:34, Vineet Gupta wrote:
> On 11/18/22 05:15, Shahab Vahedi wrote:
>> The majority of the update is about adding new definitions,
>> specially for the relocations. However, there is one rename, one
>> deletion, and one change:
>
> For completeness: And some cosmetic changes to uppercase hex digits.
Indeed, there are some cosmetic changes. If you don't mind, I'm going
to leave this part out of the commit message.
>> -#define R_ARC_JUMP_SLOT 0x37
>> +#define R_ARC_JMP_SLOT 0x37
>
> Did you build glibc with this change ? There are references to old definition.
>
> git grep R_ARC_JUMP_SLOT
>
> sysdeps/arc/dl-machine.h:199: ((((type) == R_ARC_JUMP_SLOT \
> sysdeps/arc/dl-machine.h:206:#define ELF_MACHINE_JMP_SLOT R_ARC_JUMP_SLOT
> sysdeps/arc/dl-machine.h:277: case R_ARC_JUMP_SLOT:
> sysdeps/arc/dl-machine.h:337: if (r_type == R_ARC_JUMP_SLOT)
Thank you very much for noticing this. This was a snafu on my part.
I forgot to bring the complete changes from an old downstream branch
I had. This has been fixed in v2 of the patch [1] which is now tested
by building the current master branch:
$ module load <arcv2_toolchain>
$ configure --prefix=/usr \
--with-headers=/path/to/sysroot/usr/include \
--build=x86_64-pc-linux-gnu \
--host=arc-snps-linux-gnu \
--target=arc-snps-linux-gnu \
--disable-werror \
CFLAGS="-Og -g3 -fvar-tracking-assignments" \
CXXFLAGS="-Og -g3 -fvar-tracking-assignments"
$ make
[1]
https://sourceware.org/pipermail/libc-alpha/2022-November/143536.html
--
Shahab
next prev parent reply other threads:[~2022-11-21 13:08 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 [this message]
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
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=de0e7112-4f83-03b7-3dca-a132a59635c8@synopsys.com \
--to=libc-alpha@sourceware.org \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Shahab.Vahedi@synopsys.com \
--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).