On 6/15/13 10:09 AM, Björn Steinbrink wrote:
This seems to be due to the landing pads for the function calls. Each contains one more call to drop, so the code grows quadratically with the number of allocations.
I had a patch that's bitrotted to turn off table-driven unwinding on failure entirely for rustc. This is a sledgehammer of a solution, but it also seems practical to me: if any stage of the compiler fails, then the compiler can't reasonably do anything but abort anyhow.
Patrick _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
