| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2012-10-02 | De-export the submodules of task. Part of #3583. | Graydon Hoare | -8/+7 | |
| 2012-09-30 | When a vec/str bounds check fails, include the bad index and the length of ↵ | Gareth Daniel Smith | -0/+10 | |
| the str/vec in the fail message. | ||||
| 2012-09-21 | Install new pub/priv/export rules as defaults, old rules accessible under ↵ | Graydon Hoare | -0/+1 | |
| #[legacy_exports]; | ||||
| 2012-09-13 | core: Remove old definition of rt_fail | Brian Anderson | -6/+0 | |
| 2012-09-12 | Rename core::rt_fail to core::rt_fail_ | Brian Anderson | -0/+6 | |
| 2012-09-10 | Convert 'import' to 'use'. Remove 'import' keyword. | Brian Anderson | -1/+1 | |
| 2012-09-07 | gc: Avoid walking stack above caller frame. | Elliott Slaughter | -2/+1 | |
| Mark the base GC stack frame with a sentinel value so we know when to start collecting. | ||||
| 2012-09-07 | gc: Add stack walker for new garbage collector. | Elliott Slaughter | -0/+4 | |
| Safe points are exported in a per-module list via the crate map. A C runtime call walks the crate map at startup and aggregates the list of safe points for the program. Currently the GC doesn't actually deallocate memory on malloc and free. Adding the GC at this stage is primarily of testing value. The GC does attempt to clean up exchange heap and stack-allocated resource on failure. A result of this patch is that the user now needs to be careful about what code they write in destructors, because the GC and/or failure cleanup may need to call destructors. Specifically, calls to malloc are considered unsafe and may result in infinite loops or segfaults. | ||||
| 2012-09-04 | libcore: "import" -> "use" | Patrick Walton | -4/+4 | |
| 2012-09-02 | core: warn(non_camel_case_types) everywhere, with few exceptions | Brian Anderson | -0/+1 | |
| 2012-08-14 | De-mode comm, libc, priv, rt, sync, arc. Super easy. | Ben Blum | -0/+3 | |
| 2012-08-01 | Convert ret to return | Brian Anderson | -2/+2 | |
| 2012-07-24 | Don't emit invoke instructions inside landing pads. | Elliott Slaughter | -0/+6 | |
| We can't throw an exception from inside a landing pad without corrupting the exception handler, so we have no hope of dealing with these exceptions anyway. See: http://llvm.org/docs/ExceptionHandling.html#cleanups Part of #2861. | ||||
| 2012-07-23 | Moved malloc and free upcalls into rust runtime. | Elliott Slaughter | -1/+35 | |
| 2012-07-23 | Move fail upcall into rust libcore. | Elliott Slaughter | -0/+27 | |
