Add MAKE-SEQUENCE transform
Trivial change of some DEFVARs to DEFGLOBAL
Sometimes allow MAPCAR et.al. to see compiler-macro for the funarg
Enhancement to help detect wrongly-ordered lists of files to compile.
Update OPTIMIZATIONS
Improve CONSTANTP handling of THE
Remove (safety 0) that is no longer needed for "a bootstrap problem"
Dead variables.

*COUNT-VOP-USAGES* was unused since inception.
*IN-PACK* went away in 6a9bbe6f36179cee92001a1f9ed5ff38be512644
New feature: signal a style-warning on most failures to inline.

This is a further enhancement to the full-call detector.
Among the inlining failures that won't be signaled:

- (MAPfoo #'FN x) or a quantifier (SOME, etc) in which, had the
  function been defined earlier, the compiler could have inlined,
  whereas since #'FN is a reference and not onstensibly a call,
  it does not get counted as a missed opportunity to inline.

- almost anything in build systems that enforce dependencies by not
  giving you visibility to any file except explicitly stated requisites
  *and* that create a fresh Lisp image for each step.
  At least two build systems isolate compilations as such,
  one being Fare's XCVB, the other an in-house complicated beast.
  False negatives result from the fact that the file which performs
  DECLAIM INLINE is (usually) the one that should warn, but if you
  neither compile nor load that file, then nothing knows simultaneously
  that there should not have been a full call and that there was.
  To remedy this would mean propagating codegen status across Lisp images
  by either a hideous hack involving cfasls, or a new artifact file.

But good ol' ASDF should not exhibit many false negatives.

INLINING-DEPENDENCY-FAILURE is the new condition class, the message
for which appears in a few variants (see new tests). It isn't yet
exported from SB-EXT as this code is still slightly experimental.

Meta-compile of SBCL is now expectedly much more warning-prone :-(
Quantifiers can benefit from compiler-macros now.
Eliminate a warning
Simplify the tests in /CANNOT-SHOW and eliminate an "unreachable code" warning.

This change started out with the intent of just getting rid of the warning
about (VALUES) being dead code, because the preceding ERROR kills it.

Then I observed that a KLUDGE by CSR (ca. 2002) could be removed by moving
string-dispatch later in its file, becoming a def!macro, which needs
sane-package, which is defined above in the same file.

Moreover, two of the failure modes in SUPPRESS-/SHOW-P no longer apply,
as *TRACE-OUTPUT* is set immediately in cold-init.
And since (WRITE `(EXPR= ,(EXPR) ,(OTHEREXPR) ...)) works really early,
for the most part /SHOW and /SHOW0 should be considered deprecated.

It would be great if somebody would make cold-stderr-stream work on win32.
Remove inadvertent piece of prior change.
Create far less noise with sb-show

Down to < 14000 lines of output from starting cold-sbcl.core
Be more principled in defining ATOMIC-INCF/DECF on non-raw cells.

This fixes a style-warning that occurred during building of the XC,
which is that 'late-extensions.lisp' compiles before CAS is a known
macro, so the host Lisp compiles a call to a nonexistent function
named CAS. This didn't matter because the code is target-only.
Never set :assumed-type to NIL, remove it instead.
Prefer a boxed representation for constants that are immediately returned

(with the generic calling convention that is)

Fixes lp#1398785.