wanted: compile-file verbosity which emits information about optimization settings

[Tobias C. Rittweiler]

The .verbose parameter to COMPILE-FILE is a generalized boolean, so I think it's
allowed for implementation to discriminate on different verbosity levels.

I'd like to have a value I can set *COMPILE-VERBOSE* to, and SBCL would emit
information about

  a) the initial optimization settings it's going to compile a file with

  b) report file-global change of optimization settings.

[Nikodemus Siivola (nikodemus)]

Why not do these always when :VERBOSE is true? I don't think the extra noise would be that bad.

That said, we already distinguish between :PRINT :TOP-LEVEL-FORMS (reporting each semantically toplevel form) and :PRINT #<Anything non-NIL> (the default, reporting each syntactic toplevel form) -- so adding meaning to :VERBOSE would not be a radical change.

Not opposed, I just think that it would be nice to have the additional policy information on by default.

[Douglas Katzman (dougk)]

There is very closely approximated by:

(eval-when (:compile-toplevel)
  (format t "~&Using toplevel policy ~S~%" sb-c::*policy)
  (shadow 'declaim))
(eval-when (:compile-toplevel)
  (defmacro declaim (&rest stuff)
    (format t "~&Declaiming ~S~%" stuff)
    `(cl:declaim ,@stuff)))

Don't need it in the compiler. (And in a build system that can compile 4000 files with ease as the press of a button, are you really going to want the compiler to print all that?)