Change the logging level for the optimizer logs.

original commit: feefa31401e4eccc7fbe2e60fd018e830f019254
This commit is contained in:
Vincent St-Amour 2011-09-01 18:31:17 -04:00
parent 702e78f9fa
commit bae88339d9
2 changed files with 4 additions and 4 deletions

View File

@ -214,7 +214,7 @@
(define logger (current-logger))
(add-missed-opts-to-log)
(for ([x (sort-log)])
(log-message logger 'warning
(log-message logger 'debug
(format-log-entry x)
(cons optimization-log-key x))))
@ -232,7 +232,7 @@
;; only intercepts TR log messages
(define (with-intercepted-tr-logging interceptor thunk)
(with-intercepted-logging
#:level 'warning
#:level 'debug
(lambda (l) ;; look only for optimizer messages
(when (log-message-from-tr-opt? l)
(interceptor l)))

View File

@ -181,8 +181,8 @@ can as a starting point for performance debugging.
Similar information (albeit without in-depth explanations or advice) is
available from the command line. When compiling a Typed Racket program, setting
the racket @seclink[#:doc '(lib "scribblings/reference/reference.scrbl")
"logging"]{logging} facilities to the @racket['warning] level causes Typed
"logging"]{logging} facilities to the @racket['debug] level causes Typed
Racket to display performance debugging information. Setting the Racket logging
level can be done on the command line with the @racket[-W] flag:
@commandline{racket -W warning my-typed-program.rkt}
@commandline{racket -W debug my-typed-program.rkt}