From: Mark Hatle <mark.hatle@windriver.com>
To: Manjeet Pawar <manjeet.p@samsung.com>, <yocto@yoctoproject.org>
Cc: Vaneet Narang <v.narang@samsung.com>,
ajeet.y@samsung.com, doha.hwang@samsung.com,
hakbong5.lee@samsung.com, maninder1.s@samsung.com,
pankaj.m@samsung.com
Subject: Re: [PATCH 1/1] Fix AARCH64_TLSDESC relocation conflict
Date: Tue, 3 Nov 2015 15:10:29 -0600 [thread overview]
Message-ID: <563922C5.5080505@windriver.com> (raw)
In-Reply-To: <1446551079-38517-1-git-send-email-manjeet.p@samsung.com>
On 11/3/15 5:44 AM, Manjeet Pawar wrote:
> This patch needs to be applied to 'cross_prelink_aarch64' branch.
> It fixes tls1, tls2, tls4, tls5, tls6 test cases of prelink testsuite.
> tls3 gets failed but this test case fails without prelink as well on AARCH64
>
> Signed-off-by: Vaneet Narang <v.narang@samsung.com>
> Signed-off-by: Manjeet Pawar <manjeet.p@samsung.com>
> ---
> src/arch-aarch64.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/arch-aarch64.c b/src/arch-aarch64.c
> index e04dd6e..6499c68 100644
> --- a/src/arch-aarch64.c
> +++ b/src/arch-aarch64.c
> @@ -375,7 +375,7 @@ aarch64_prelink_conflict_rela (DSO *dso, struct prelink_info *info,
> break;
> case R_AARCH64_TLSDESC:
> tls = conflict ? conflict->lookup.tls : info->curtls;
> - ret->r_addend = rela->r_addend + tls->offset;
> + ret->r_addend = value + rela->r_addend + tls->offset;
> break;
> default:
> error (0, 0, "%s: Unknown AARCH64 relocation type %d", dso->filename,
>
I'm still getting segfaults here.
The way I am testing is building a Yocto Project (jethro) system
core-image-base, and adding to it:
"packagegroup-core-buildessential,libelf,elfutils-dev,binutils-staticdev,glibc-staticdev"
The copying a checked out version of the prelink-cross repository with the
prelink_cross_aarch64 branch checked out.
On the target:
autoreconf -if
./configure
make
make -C testsuite check
Most tests still fail, and all of the TLS tests result in a segfault.
(I do have the 'aarch64/dl-machine.h: Fix load-address for prelink support'
applied to my glibc. Are there any other patches that may need to be applied?)
--Mark
next prev parent reply other threads:[~2015-11-04 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 11:44 [PATCH 1/1] Fix AARCH64_TLSDESC relocation conflict Manjeet Pawar
2015-11-03 21:10 ` Mark Hatle [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-04 5:58 Vaneet Narang
2015-11-06 7:09 Vaneet Narang
2015-11-06 14:26 ` Mark Hatle
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=563922C5.5080505@windriver.com \
--to=mark.hatle@windriver.com \
--cc=ajeet.y@samsung.com \
--cc=doha.hwang@samsung.com \
--cc=hakbong5.lee@samsung.com \
--cc=maninder1.s@samsung.com \
--cc=manjeet.p@samsung.com \
--cc=pankaj.m@samsung.com \
--cc=v.narang@samsung.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.