public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Neal Frager <neal.frager@amd.com>, binutils@sourceware.org
Cc: ibai.erkiaga-elorza@amd.com, nagaraju.mekala@amd.com,
	mark.hatle@amd.com, sadanand.mutyala@amd.com,
	appa.rao.nali@amd.com, vidhumouli.hunsigida@amd.com,
	luca.ceresoli@bootlin.com
Subject: Re: [PATCH v1 1/1] bfd: microblaze: Fix bug in TLSTPREL Relocation
Date: Wed, 27 Sep 2023 16:24:38 +0100	[thread overview]
Message-ID: <73a79b01-e095-fc7a-5b34-2b0308fe427e@redhat.com> (raw)
In-Reply-To: <20230927124918.1584074-1-neal.frager@amd.com>

Hi Neal,

> Fixed the problem related to the fixup/relocations TLSTPREL.
> When the fixup is applied the addend is not added at the correct offset
> of the instruction. The offset is hard coded considering its big endian
> and it fails for Little endian. This patch allows support for both
> big & little-endian compilers.
> 
> This patch has been tested for years of AMD Xilinx Yocto
> releases as part of the following patch set:
> 
> https://github.com/Xilinx/meta-xilinx/tree/master/meta-microblaze/recipes-devtools/binutils/binutils
> 
> Signed-off-by: nagaraju <nagaraju.mekala@amd.com>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
>   bfd/elf32-microblaze.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)

Patch approved, please apply.

Cheers
   Nick



  reply	other threads:[~2023-09-27 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 12:49 Neal Frager
2023-09-27 15:24 ` Nick Clifton [this message]
2023-09-29 15:36   ` Michael Eager

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=73a79b01-e095-fc7a-5b34-2b0308fe427e@redhat.com \
    --to=nickc@redhat.com \
    --cc=appa.rao.nali@amd.com \
    --cc=binutils@sourceware.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=mark.hatle@amd.com \
    --cc=nagaraju.mekala@amd.com \
    --cc=neal.frager@amd.com \
    --cc=sadanand.mutyala@amd.com \
    --cc=vidhumouli.hunsigida@amd.com \
    /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).