public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch hjl/mpx/master created. cf8a2373240aaa818c5099f59edfe184536bdee1
Date: Mon, 18 Nov 2013 18:00:00 -0000	[thread overview]
Message-ID: <> (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/mpx/master has been created
        at  cf8a2373240aaa818c5099f59edfe184536bdee1 (commit)

- Log -----------------------------------------------------------------;h=cf8a2373240aaa818c5099f59edfe184536bdee1

commit cf8a2373240aaa818c5099f59edfe184536bdee1
Author: H.J. Lu <>
Date:   Sun Nov 17 10:30:28 2013 -0800

    Add R_X86_64_PC32_BND/R_X86_64_PLT32_BND suppor to gold
    	* x86_64.h (R_X86_64_PC32_BND): New.
    	(R_X86_64_PLT32_BND): Likewise.
    2013-11-17  H.J. Lu  <>
    	* (Target_x86_64<size>::Scan::get_reference_flags):
    	Handle R_X86_64_PC32_BND and R_X86_64_PLT32_BND just like
    	R_X86_64_PC32 and R_X86_64_PLT32, respectively.
    	(Target_x86_64<size>::Scan::local): Likewise.
    	(Target_x86_64<size>::Scan::global): Likewise.
    	(Target_x86_64<size>::Relocate::relocate): Likewise.
    	(Target_x86_64<size>::Scan::check_non_pic(): Handle
    	* testsuite/ (check_PROGRAMS): Add
    	(exception_x86_64_bnd_test_SOURCES): New macro.
    	(exception_x86_64_bnd_test_DEPENDENCIES): Likewise.
    	(exception_x86_64_bnd_test_LDFLAGS): Likewise.
    	(exception_x86_64_bnd_test_LDADD): Likewise.
    	(exception_x86_64_bnd_1.o): New rule.
    	(exception_x86_64_bnd_2.o): Likewise.
    	* testsuite/ Regenerated.


gdb and binutils

                 reply	other threads:[~2013-11-18 18:00 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).