- 20 4月, 2011 5 次提交
-
-
由 Graydon Hoare 提交于
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
由 Marijn Haverbeke 提交于
-
- 19 4月, 2011 17 次提交
-
-
由 Marijn Haverbeke 提交于
See https://github.com/graydon/rust/wiki/Logging-vision The runtime logging categories are now treated in the same way as modules in compiled code. Each domain now has a log_lvl that can be used to restrict the logging from that domain (will be used to allow logging to be restricted to a single domain). Features dropped (can be brought back to life if there is interest): - Logger indentation - Multiple categories per log statement - I possibly broke some of the color code -- it confuses me
-
由 Marijn Haverbeke 提交于
-
由 Marijn Haverbeke 提交于
-
由 Marijn Haverbeke 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Graydon Hoare 提交于
-
由 Patrick Walton 提交于
-
wrong on Windows.
-
由 Graydon Hoare 提交于
-
-
由 Lindsey Kuper 提交于
This is basically so people don't confuse a Ref.Item.Type with a Ref.Type.
-
由 Patrick Walton 提交于
-
由 Marijn Haverbeke 提交于
Uncomment log initialization.
-
由 Marijn Haverbeke 提交于
Will be restored as soon as I find a way for the runtime to figure out whether it is on rustboot or rustc.
-
- 18 4月, 2011 14 次提交
-
-
由 Marijn Haverbeke 提交于
Apparently it can't live in the main binary, since on non-Linux platforms, dynamics libs won't find symbols in the binary. This removes the crate_map pointer from rust_crate again, and instead passes it as an extra argument to rust_start. Rustboot doesn't pass this argument, but supposedly that's okay as long as we don't actually use it on that platform.
-
-
由 Marijn Haverbeke 提交于
This overloads the meaning of RUST_LOG to also allow 'module.submodule' or 'module.somethingelse=2' forms. The first turn on all logging for a module (loglevel 3), the second sets its loglevel to 2. Log levels are: 0: Show only errors 1: Errors and warnings 2: Errors, warnings, and notes 3: Everything, including debug logging Right now, since we only have one 'log' operation, everything happens at level 1 (warning), so the only meaningful thing that can be done with the new RUST_LOG support is disable logging (=0) for some modules. TODOS: * Language support for logging at a specific level * Also add a log level field to tasks, query the current task as well as the current module before logging (log if one of them allows it) * Revise the C logging API to conform to this set-up (globals for per-module log level, query the task level before logging, stop using a global mask) Implementation notes: Crates now contain two extra data structures. A 'module map' that contains names and pointers to the module-log-level globals for each module in the crate that logs, and a 'crate map' that points at the crate's module map, as well as at the crate maps of all external crates it depends on. These are walked by the runtime (in rust_crate.cpp) to set the currect log levels based on RUST_LOG. These module log globals are allocated as-needed whenever a log expression is encountered, and their location is hard-coded into the logging code, which compares the current level to the log statement's level, and skips over all logging code when it is lower.
-
由 Marijn Haverbeke 提交于
-
由 Marijn Haverbeke 提交于
-
由 Marijn Haverbeke 提交于
This reduces crate_ctxt copying (which unfortunately did not result in a noticeable speedup), and makes the role of that type a bit more clear.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
Not totally confident this is desirable. The alternative would be to make it a compile error.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
Add missing tests
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
- 17 4月, 2011 4 次提交
-
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-