public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch binutils-2_24-branch updated. 268121417c4844cbb1d533cd5e0a2e273442d718
Date: Thu, 07 Nov 2013 18:02: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, binutils-2_24-branch has been updated
       via  268121417c4844cbb1d533cd5e0a2e273442d718 (commit)
      from  588f35c9cf6a64722aba60993a26dda12ee33db6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------;h=268121417c4844cbb1d533cd5e0a2e273442d718

commit 268121417c4844cbb1d533cd5e0a2e273442d718
Author: Roland McGrath <>
Date:   Wed Nov 6 14:47:05 2013 -0800

    Set CPU type in BFD backend for x86_64-nacl* and i?86-nacl* targets
    	* archures.c (bfd_mach_i386_nacl): Fix definition so it doesn't
    	collide with bfd_mach_l1om.
    	* bfd-in2.h: Regenerate.
    	* elf32-i386.c (elf32_i386_nacl_elf_object_p): New function.
    	(elf_backend_object_p): Use that in elf32-i386-nacl definition.
    	* elf64-x86-64.c (elf64_x86_64_nacl_elf_object_p): New function.
    	(elf_backend_object_p): Use that in elf64-x86-64-nacl definition.
    	(elf32_x86_64_nacl_elf_object_p): New function.
    	(elf_backend_object_p): Use that in elf32-x86-64-nacl definition.
    	* objdump.c (dump_dwarf): Grok bfd_mach_x86_64_nacl and
    	bfd_mach_x64_32_nacl as equivalent to bfd_mach_x86_64.
    	* ld-x86-64/x86-64.exp (mixed1, mixed2): Loosen error string match
    	so it accepts "i386:nacl" in place of "i386".
    	* ld-x86-64/ilp32-2.d: Likewise.
    	* ld-x86-64/ilp32-3.d: Likewise.
    	* ld-x86-64/lp64-2.d: Likewise.
    	* ld-x86-64/lp64-3.d: Likewise.
    (cherry picked from commit 64b384e1e821cedccefa24f6d5bb82d353546ca1)


Summary of changes:
 bfd/ChangeLog                     |   13 +++++++++++++
 bfd/archures.c                    |    8 ++++----
 bfd/bfd-in2.h                     |    8 ++++----
 bfd/elf32-i386.c                  |   11 +++++++++++
 bfd/elf64-x86-64.c                |   20 +++++++++++++++++++-
 binutils/ChangeLog                |    5 +++++
 binutils/objdump.c                |    2 ++
 ld/testsuite/ChangeLog            |    9 +++++++++
 ld/testsuite/ld-x86-64/ilp32-2.d  |    2 +-
 ld/testsuite/ld-x86-64/ilp32-3.d  |    2 +-
 ld/testsuite/ld-x86-64/lp64-2.d   |    2 +-
 ld/testsuite/ld-x86-64/lp64-3.d   |    2 +-
 ld/testsuite/ld-x86-64/x86-64.exp |    4 ++--
 13 files changed, 73 insertions(+), 15 deletions(-)

gdb and binutils

                 reply	other threads:[~2013-11-07 18:02 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).