public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: hjl@sourceware.org
To: src-cvs@sourceware.org
Subject: gdb and binutils branch hjl/copyreloc created. 8efba8ea4ebe0d2cf34ee71f06f6b601a12004ee
Date: Wed, 03 Dec 2014 13:34:00 -0000	[thread overview]
Message-ID: <20141203133416.29755.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, hjl/copyreloc has been created
        at  8efba8ea4ebe0d2cf34ee71f06f6b601a12004ee (commit)

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8efba8ea4ebe0d2cf34ee71f06f6b601a12004ee

commit 8efba8ea4ebe0d2cf34ee71f06f6b601a12004ee
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Tue Dec 2 15:14:28 2014 -0800

    X86-64: Allow copy relocs for building PIE
    
    This patch allows copy relocs for non-GOT pc-relative relocation in PIE.
    
    bfd/
    
    	* elf64-x86-64.c (elf_x86_64_create_dynamic_sections): Always
    	allow copy relocs for building executables.
    	(elf_x86_64_adjust_dynamic_symbol): Allocate copy relocs for
    	PIE.
    	(elf_x86_64_allocate_dynrelocs): For PIE, discard space for
    	relocs against symbols which turn out to need copy relocs.
    	(elf_x86_64_relocate_section): Don't copy a pc-relative
    	relocation into the output file if the symbol needs copy reloc.
    
    ld/testsuite/
    
    	* ld-x86-64/copyreloc-lib.c: New file.
    	* ld-x86-64/copyreloc-main.c: Likewise.
    	* ld-x86-64/copyreloc-main.out: Likewise.
    	* ld-x86-64/copyreloc-main1.rd: Likewise.
    	* ld-x86-64/copyreloc-main2.rd: Likewise.
    
    	* ld-x86-64/x86-64.exp: Run copyreloc tests.

-----------------------------------------------------------------------


hooks/post-receive
-- 
gdb and binutils


                 reply	other threads:[~2014-12-03 13:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141203133416.29755.qmail@sourceware.org \
    --to=hjl@sourceware.org \
    --cc=src-cvs@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).