Re:Rust gets a faster sort implementation
by mastax on Wednesday December 14, 2016 @12:56PM
(#13178066)
As an example of this, Zoxc has been trying to get stack probe support into LLVM for two years to no avail [0]. This is important to make sure that stack overflow or buffer overrun actually trigger the guard page and cause termination.
I admit it's not really fair to LLVM to pick on one patch like this but it's frustrating to me even as an outsider.
Re:Rust gets a faster sort implementation
by whitequark_ on Wednesday December 14, 2016 @03:33PM
(#13179399)
Zoxc has repeatedly refused reasonable requests to alter the patch to fit the standards of upstream. Because of this (and because I am rather tired of not having stack probes, with my embedded system not having functional guard pages), I'll make a hostile fork of their patch soon and get it through the pipeline. Stay tuned.
Re:Rust gets a faster sort implementation
by dbaupp on Tuesday December 20, 2016 @01:47PM
(#13222681)
Late comment, but aren't stack probes entirely predicated on having working guard pages? I.e. they only exist to guarantee that the guard page is accessed before anything else, when a frame is larger than the page.
Re:Rust gets a faster sort implementation
by mastax on Wednesday December 14, 2016 @06:17PM
(#13180689)
Ah, interesting. I hadn't gleamed that from the threads. It's great to hear that there's a chance that this will be supported though!
Also, the fact that the CI triggers and lets you know whether your change causes any collateral damage before you merge takes away a lot of the fear factor of contributing. This is also in stark contrast to LLVM's "merge it if it LGTM, revert it soon after when we find out what it broke."