- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Add support for the 'invpcid' instruction to binutils and DDB's
disassembler on amd64.

MFC after: 1 month

add support for AES and PCLMULQDQ instructions to binutils...

Thanks to Mike Belopuhov for the pointer to the OpenBSD patch, though
OpenBSD's gcc is very different that it only helped w/ where to modify,
not how... Thanks to jhb for some early reviews...

Reviewed by: imp, kib
MFC after: 1 month

Add support for the 'invept' and 'invvpid' instructions. Beyond simply
adding appropriate table entries, the assembler had to be adjusted as
these are the first non-SSE instructions to use a 3-byte opcode (and a
mandatory prefix to boot).

MFC after: 1 month

Add support for the 'xsave', 'xrstor', 'xsaveopt', 'xgetbv', and 'xsetbv'
instructions. I reimplemented this from scratch based on the Intel
manuals and the existing support for handling the fxsave and fxrstor
instructions. This will let us use these instructions natively with GCC
rather than hardcoding the opcodes in hex.

Reviewed by: kib
MFC after: 1 month

Merge binutils 2.17.50 to head. This brings a number of improvements to
x86 CPU support, better support for powerpc64, some new directives, and
many other things. Bump __FreeBSD_version, and add a note to UPDATING.

Thanks to the many people that have helped to test this.

Obtained from: projects/binutils-2.17

Update HEAD with the stock binutils_2_15_20040523 file.

Try to keep CVS from pissing over the next binutils import by returning
to purely stock files.

Bring the binutils_2_13_20021110 snap version of this to the HEAD branch.

Bring the binutils_2_12_20020622 snap version of this to the HEAD branch.

Bring the binutils_2_12_20020410 snap version of this to the HEAD branch.

Bring the binutils_2_12_20020221_snap version of this to the HEAD branch.

Bring the binutils_2_12_cvs_20020125 version of this to the HEAD branch.

Bring the binutils_2_11_cvs_20011031 version of this to the HEAD branch.

We use the stock (2.11.2) version of this now.

Return to the vendor's version of this file.

Use the stock file now. The Binutils maintainers accepted our rev 1.2
changes (don't use "/" to start a comment).

Merge in rev 1.2 (don't use "/" to start a comment).

Turn a warning into an error. Occurances of that warning generate bad
-fpic code that damages symbol locations at runtime.

The only know occurance in our tree (src and ports) was locatime.c,
which was just changed to generate code that doesn't trigger the
problem.

This is a workaround, the real cause is that our gas doesn't
understand code our gcc generates for some -O -fpic code. They are
expected to be back in sync soon, but until then (including
4.0-RELEASE) we need to prevent people from using bad -fpic code.

PR: avoids such things as in bin/16862
Submitted by: bde
Approved by: jkh

Resolve conflicts from import of binutils-2.9.1.

Submitted by: Doug Rabson <dfr>

Don't use "/" as a comment starter. In some FreeBSD sources, "/"
means divide (duh).

This commit was generated by cvs2svn to compensate for changes in r33965,
which included commits to RCS files with non-trunk default branches.

Initial import of GNU binutils version 2.8.1. Believe it or not,
this is heavily stripped down.