rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2011-05-26	More delicious dead code removal from runtime, upcalls.	Graydon Hoare	-51/+0

2011-05-24	Only one gc glue.	Rafael Ávila de Espíndola	-5/+0

2011-05-24	There is only one yield glue.	Rafael Ávila de Espíndola	-5/+0

2011-05-24	Remove dead code for unwind_glue.	Rafael Ávila de Espíndola	-5/+0

2011-05-24	There is only one activate function now.	Rafael Ávila de Espíndola	-5/+0

2011-05-18	One exit_task_glue to rule them all.	Rafael Ávila de Espíndola	-5/+0

2011-04-19	Overhaul logging system in runtime	Marijn Haverbeke	-2/+2
	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
2011-04-18	Update foregoing patches to leave rust_crate alone.	Marijn Haverbeke	-86/+0
	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.
2011-04-18	Make log the log level configurable per module	Marijn Haverbeke	-0/+86
	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.
2011-04-07	Move to macro-based logging checks in the C++ code	Marijn Haverbeke	-1/+1
	No functions should be called for log statements that turn out to be inactive.
2010-07-20	Be a little more careful before assuming we have crate debuginfo and abbrevs ↵	Graydon Hoare	-4/+12
	to read.
2010-06-25	Add rust_task::gc(size_t args) method that drops us back into the GC glue.	Graydon Hoare	-0/+5

2010-06-23	Populate tree.	Graydon Hoare	-0/+63