Teach monitor's 'dump' command about 8-byte words.
Placate Darwin C compiler with an explicit function prototype.
Remove ASSIGN-SETF-MACRO's secondary test for fboundness of SETF fun.

The new code is behaviorally different in a subtle way.  The old didn't
didn't warn if a setf function was defined earlier in the same file
unless in eval-when :compile-toplevel. Whereas if (SETF F) had come
from a previously loaded file, you did get a style-warning upon
definition of the macro. Now either way style-warns.

There is no change in the signaling of a full warning if the compiler
has *assumed* a setf function to exist when the macroish setter is
defined, because that suggests something was compiled wrong.

This is almost but not entirely like the patch I proposed on sbcl-devel.
The unanticipated problems were mainly during xc because :where-from
changes what it reports for a function name that has no binding.
This might possibly warn about a few things in xc that it didn't before.
CURRENT-THREAD-OFFSET-SAP, take 2, now with less magic.
Implement DEFINE-LOAD-TIME-GLOBAL.

This is the patch proposed on sbcl-devel (ca. November 2013)
with alterations for 2 out of 3 concerns raised by Nikodemus.

Indeed users can not roll their own equivalent of the new macro
using just the new proclamation. It's confusing to expose the
feature, as it would mean introducing another thing like
  (DECLAIM (EVENTUALLY-ALWAYS-BOUND X)) ; *HYPOTHETICAL*
and then explaining how compilation "times" a/k/a "situations" are
not quite the same as "now" and "eventually", and why 2N choices
exist for one concept. YAGNI/Occam's Razor come to mind.

Were a user to try something like
  (eval-when (:load-toplevel) (proclaim '(always-bound x)))
it can not possibly have any unusual effect due to PROCLAIM being
an ordinary function, whereas eval-when :compile-toplevel of same
certainly means that X is right now always bound.
So only the new macro is documented, not its implementation.

Closes lp#1253688
Adjust boundary test in x86-64 ALLOCATION sequence.
Unbreak SIMPLIFY-NAMESTRING
Improve x86-64 ALLOCATE-VECTOR- for constant lengths.
Reject defstruct syntax having unclear intent.
Fix more pprinting glitches in backquoted vectors
Re-fix *reader-package* inside sharp-{plus,minus}
Don't try to allocate huge vectors in a thread region.

This isn't an optimization so much as "why were we doing that?"
Avoid deprecated function in test for bug 881445
Make the newly-added 'on-error' optional in do-forms-from-info

This is the simplest possible change which arbitrarily deems
that errors should be reported as errors in LOAD.
Stop COMMUTATIVE-ARG-SWAP from producing undumpable structures.

If the form produces an error such undumpable structures will prevent
the error message from being dumped into the FASL.

COMMUTATIVE-ARG-SWAP manages to do so by wrapping the non-constant
variable in (truly-the type), to facilitate type propagation.

Get rid of COMMUTATIVE-ARG-SWAP completely, introduce a new known
attribute, COMMUTATIVE, and let IR1-OPTIMIZE-COMBINATION to perform
argument swapping before applying any transforms and without
discarding any type derivation already performed on the combination.

Fixes lp#1276282.
Add double-width compare-and-exchange instructions for x86oid.

Also add a test for the CPUID instruction.

There are new private functions for the enlightened.
These could be used as the implementation of a publicized CAS
expander for something like
  (CAS (car+cdr my-cons) ...) ; Don't do this (not implemented)
but I didn't think that "shoehorning" these into CAS was better
than just providing the functions.
Improve LOGBITP of constant 2nd arg
Unbreak SB-COVER
Ensure that the fopcompiler signals a warning on undefined functions.

Made a new file for fopcompiler tests that shouldn't first be compiled.
Also moved the fasload-print test to a better location.
Small cleanups in src/compiler/x86[-64]/insts.lisp.

On both platforms, remove a redundant instruction format definition:
TWO-BYTES was defined twice, identically. (The repetition seems not
to have done any harm.)

Break overly long lines and, on x86-64, update a comment.