{"push_id":753250584,"size":1,"distinct_size":1,"ref":"refs/heads/remove-morestack","head":"acbdf0a1bded880011cfff5f487066a8d16f2e0b","before":"acb896153e4b3a94260eb36c34d19e3dcfdec6b2","commits":[{"sha":"acbdf0a1bded880011cfff5f487066a8d16f2e0b","author":{"email":"60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","name":"Alex Crichton"},"message":"Remove morestack support\n\nThis commit removes all morestack support from the compiler which entails:\n\n* Segmented stacks are no longer emitted in codegen.\n* We no longer build or distribute libmorestack.a\n* The `stack_exhausted` lang item is no longer required\n\nThe only current use of the segmented stack support in LLVM is to detect stack\noverflow. This is no longer really required, however, because we already have\nguard pages for all threads and registered signal handlers watching for a\nsegfault on those pages (to print out a stack overflow message). Additionally,\nmajor platforms (aka Windows) already don't use morestack.\n\nThis means that Rust is by default less likely to catch stack overflows because\nif a function takes up more than one page of stack space it won't hit the guard\npage. This is what the purpose of morestack was (to catch this case), but it's\nbetter served with stack probes which have more cross platform support and no\nruntime support necessary. Until LLVM supports this for all platform it looks\nlike morestack isn't really buying us much.\n\ncc #16012 (still need stack probes)\nCloses #26458 (a drive-by fix to help diagnostics on stack overflow)","distinct":true,"url":"https://api.github.com/repos/alexcrichton/rust/commits/acbdf0a1bded880011cfff5f487066a8d16f2e0b"}]}