Andreas Arnez 4ef9f41a95 S390: Support new vector register sections
The IBM z13 has new 128-bit wide vector registers v0-v31, where v0-v15
include the existing 64-bit wide floating point registers.  The Linux
kernel presents the vector registers as two additional register sets,
one for the right halves of v0-v15 and another one for the full
registers v16-v31.  Thus a new core file may contain two new register
note sections, and this patch adds support to binutils for them.

bfd/
	* elf-bfd.h (elfcore_write_s390_vxrs_low): Add prototype.
	(elfcore_write_s390_vxrs_high): Likewise.
	* elf.c (elfcore_grok_s390_vxrs_low): New function.
	(elfcore_grok_s390_vxrs_high): New function.
	(elfcore_grok_note): Call them.
	(elfcore_write_s390_vxrs_low): New function.
	(elfcore_write_s390_vxrs_high): New function.
	(elfcore_write_register_note): Call them.

binutils/
	* readelf.c (get_note_type): Add NT_S390_VXRS_LOW and
	NT_S390_VXRS_HIGH.

include/elf/
	* common.h (NT_S390_VXRS_LOW): New macro.
	(NT_S390_VXRS_HIGH): Likewise.
2015-02-20 10:39:53 +01:00
..
2015-02-11 10:04:47 +00:00
2015-01-28 16:25:18 +10:30
2012-11-08 03:03:26 +00:00
2015-02-14 23:41:54 +10:30
2015-01-28 16:25:18 +10:30
2015-02-14 23:41:54 +10:30
2015-02-14 23:41:54 +10:30
2012-12-10 12:48:03 +00:00
2014-03-05 22:16:15 +10:30
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2012-12-10 12:48:03 +00:00
2013-02-04 05:10:44 +00:00
2012-12-10 12:48:03 +00:00
2014-03-05 22:16:15 +10:30
2014-03-05 22:16:15 +10:30
2014-03-05 22:16:15 +10:30
2015-01-28 16:25:18 +10:30
2014-07-04 13:40:28 +09:30
2015-01-28 16:25:18 +10:30
2015-01-28 16:25:18 +10:30
2015-01-28 16:25:18 +10:30
2015-02-15 19:07:03 +10:30
2015-01-19 19:37:45 +10:30
2015-01-28 16:25:18 +10:30
2015-01-28 18:30:54 +10:30
2015-02-19 14:14:52 +10:30
2015-02-11 10:04:47 +00:00
2015-02-11 10:04:47 +00:00
2015-02-11 10:04:47 +00:00
2015-02-11 10:04:47 +00:00
2015-02-14 23:41:54 +10:30
2015-02-11 10:04:47 +00:00
2015-01-28 16:25:18 +10:30
2015-01-28 16:25:18 +10:30
2015-02-14 23:41:54 +10:30
2015-01-28 16:25:18 +10:30
2015-02-11 10:04:47 +00:00
2015-01-28 16:25:18 +10:30
2015-02-19 22:08:05 +10:30
2015-02-20 00:00:08 +00:00
2014-10-15 10:21:25 +02:00

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

BFD is an object file library.  It permits applications to use the
same routines to process object files regardless of their format.

BFD is used by the GNU debugger, assembler, linker, and the binary
utilities.

The documentation on using BFD is scanty and may be occasionally
incorrect.  Pointers to documentation problems, or an entirely
rewritten manual, would be appreciated.

There is some BFD internals documentation in doc/bfdint.texi which may
help programmers who want to modify BFD.

BFD is normally built as part of another package.  See the build
instructions for that package, probably in a README file in the
appropriate directory.

BFD supports the following configure options:

  --target=TARGET
	The default target for which to build the library.  TARGET is
	a configuration target triplet, such as sparc-sun-solaris.
  --enable-targets=TARGET,TARGET,TARGET...
	Additional targets the library should support.  To include
	support for all known targets, use --enable-targets=all.
  --enable-64-bit-bfd
	Include support for 64 bit targets.  This is automatically
	turned on if you explicitly request a 64 bit target, but not
	for --enable-targets=all.  This requires a compiler with a 64
	bit integer type, such as gcc.
  --enable-shared
	Build BFD as a shared library.
  --with-mmap
	Use mmap when accessing files.  This is faster on some hosts,
	but slower on others.  It may not work on all hosts.

Report bugs with BFD to bug-binutils@gnu.org.

Patches are encouraged.  When sending patches, always send the output
of diff -u or diff -c from the original file to the new file.  Do not
send default diff output.  Do not make the diff from the new file to
the original file.  Remember that any patch must not break other
systems.  Remember that BFD must support cross compilation from any
host to any target, so patches which use ``#ifdef HOST'' are not
acceptable.  Please also read the ``Reporting Bugs'' section of the
gcc manual.

Bug reports without patches will be remembered, but they may never get
fixed until somebody volunteers to fix them.

Copyright (C) 2012-2015 Free Software Foundation, Inc.

Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.