https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.6.0 2015-12-02T17:19:10+00:00 2015-12-02T17:19:10+00:00 Björn Steinbrink bsteinbr@gmail.com 2015-12-02T17:09:33+00:00 urn:sha1:d7ccea6c1caf63e5245e357899a67d9f2e7db0b1 This pass causes mis-optimizations in some cases and is probably no longer really important for us, so let's disable it for now. Fixes #30081 2015-11-20T00:58:23+00:00 Brian Anderson banderson@mozilla.com 2015-11-19T19:32:16+00:00 urn:sha1:99741700e54ce98c12eb754b60917de21c75c2f4 2015-10-24T09:42:23+00:00 Seo Sanghyeon sanxiyn@gmail.com 2015-10-24T09:42:23+00:00 urn:sha1:b285f9202590050a7b480a99a074673630b11f4f 2015-10-18T14:40:45+00:00 Björn Steinbrink bsteinbr@gmail.com 2015-10-18T14:40:45+00:00 urn:sha1:92276dc616195f327ff793235fd81f498b565b8b Fixes #28947 2015-10-13T06:11:59+00:00 Seo Sanghyeon sanxiyn@gmail.com 2015-10-13T06:11:59+00:00 urn:sha1:22dc40821770db567915250af3f8c2fdb0c1ab81 2015-10-08T18:49:31+00:00 Cristi Cobzarenco cristi.cobzarenco@gmail.com 2015-10-07T22:11:25+00:00 urn:sha1:4b308b44e1d8204702f6912dda4dfc404aa2a87d 2015-09-29T23:56:35+00:00 Alex Crichton alex@alexcrichton.com 2015-09-18T17:19:23+00:00 urn:sha1:27dd6dd3dbe92debaac7d54c8405a3d3af1c4daf Travis CI has new infrastructure using the Google Compute Engine which has both faster CPUs and more memory, and we've been encouraged to switch as it should help our build times! The only downside currently, however, is that IPv6 is disabled, causing a number of standard library tests to fail. Consequently this commit tweaks our travis config in a few ways: * ccache is disabled as it's not working on GCE just yet * Docker is used to run tests inside which reportedly will get IPv6 working * A system LLVM installation is used instead of building LLVM itself. This is primarily done to reduce build times, but we want automation for this sort of behavior anyway and we can extend this in the future with building from source as well if needed. * gcc-specific logic is removed as the docker image for Ubuntu gives us a recent-enough gcc by default. 2015-09-11T15:40:37+00:00 Björn Steinbrink bsteinbr@gmail.com 2015-09-11T09:46:01+00:00 urn:sha1:e8c398d05c92d4cdd7b3528b892355e0c000131b 2015-09-02T16:29:54+00:00 Alex Crichton alex@alexcrichton.com 2015-09-02T16:21:52+00:00 urn:sha1:5cb6b3eb531487896b38df019f3f6a9055fbe494 This is a rebase of our few small patches on top of the release of LLVM 3.7, picking up those last few bug fixes on the way up to 3.7! 2015-08-10T23:35:44+00:00 Alex Crichton alex@alexcrichton.com 2015-07-27T20:41:35+00:00 urn:sha1:7a3fdfbf674a08b7f6fd32c9124e52924a2f9a1c This commit removes all morestack support from the compiler which entails: * Segmented stacks are no longer emitted in codegen. * We no longer build or distribute libmorestack.a * The `stack_exhausted` lang item is no longer required The only current use of the segmented stack support in LLVM is to detect stack overflow. This is no longer really required, however, because we already have guard pages for all threads and registered signal handlers watching for a segfault on those pages (to print out a stack overflow message). Additionally, major platforms (aka Windows) already don't use morestack. This means that Rust is by default less likely to catch stack overflows because if a function takes up more than one page of stack space it won't hit the guard page. This is what the purpose of morestack was (to catch this case), but it's better served with stack probes which have more cross platform support and no runtime support necessary. Until LLVM supports this for all platform it looks like morestack isn't really buying us much. cc #16012 (still need stack probes) Closes #26458 (a drive-by fix to help diagnostics on stack overflow)