public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Cupertino Miranda <Cupertino.Miranda@synopsys.com>,
	       binutils@sourceware.org
Cc: Francois.Bedard@synopsys.com, Claudiu.Zissulescu@synopsys.com
Subject: Re: [PATCH 5/5] Dynamic TLS GOT entries would not be relocated.
Date: Fri, 19 Aug 2016 07:54:00 -0000	[thread overview]
Message-ID: <928a3aab-56ea-88e7-ac42-ad4d7a07e4c8@redhat.com> (raw)
In-Reply-To: <20160816155116.23937-6-cmiranda@synopsys.com>

Hi Cupertino,

> bfd/ChangeLog:
> 
> Cupertino Miranda  <cmiranda@synopsys.com>
> 
> 	elf32-arc.c (elf_arc_relocate_section): Changed.

Why ?


Cheers
  Nick

  reply	other threads:[~2016-08-19  7:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 15:51 [PATCH 0/5] Fixes / improvements to ARC BFD target support Cupertino Miranda
2016-08-16 15:51 ` [PATCH 2/5] Content for TLS_IE_GOT not written to .got Cupertino Miranda
2016-08-19  7:43   ` Nick Clifton
2016-08-24 14:55     ` Cupertino Miranda
2016-08-25 10:59       ` Nick Clifton
2016-08-16 15:51 ` [PATCH 1/5] Fixes to legacy relocations Cupertino Miranda
2016-08-19  7:41   ` Nick Clifton
2016-08-16 15:51 ` [PATCH 4/5] Fixed -init, -fini linker options Cupertino Miranda
2016-08-19  7:54   ` Nick Clifton
2016-08-16 15:51 ` [PATCH 5/5] Dynamic TLS GOT entries would not be relocated Cupertino Miranda
2016-08-19  7:54   ` Nick Clifton [this message]
2016-08-24 14:56     ` Cupertino Miranda
2016-08-25 11:03       ` Nick Clifton
2016-08-16 15:51 ` [PATCH 3/5] Several fixes related to ARC PIE support Cupertino Miranda
2016-08-19  7:53   ` Nick Clifton
2016-08-24 14:55     ` Cupertino Miranda
2016-08-25 11:06       ` Nick Clifton
2016-08-19  7:40 ` [PATCH 0/5] Fixes / improvements to ARC BFD target support Nick Clifton
2016-08-24 14:53   ` Cupertino Miranda

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=928a3aab-56ea-88e7-ac42-ad4d7a07e4c8@redhat.com \
    --to=nickc@redhat.com \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=Cupertino.Miranda@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=binutils@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).