- 14 9月, 2015 1 次提交
-
-
由 Sean Bowe 提交于
Fixed regression in associated item resolution with default type parameters that reference Self in traits.
-
- 13 9月, 2015 4 次提交
-
-
由 bors 提交于
This is something that I wish I had when I started contributing to Rust (not that long ago :). I plan on writing a manual for bors and the rust testing setup too, if there isn't one already.
-
由 bors 提交于
-
由 bors 提交于
- Headlines begin at 1st level now like the rest of the book - All Headlines a blank line above and below - Fix links in this chapter's TOC r? @steveklabnik
- 12 9月, 2015 14 次提交
-
-
由 Andrea Canciani 提交于
and regenerate the platform intrinsics source files.
-
由 christopherdumas 提交于
-
由 Tobias Bucher 提交于
-
由 bors 提交于
The style `[name][]` does not work with Pandoc, whereas `[name]` does. I hope hoedown accepts this as well. r? @steveklabnik
-
由 Pascal Hertleif 提交于
The style `[name][]` does not work with Pandoc, whereas `[name]` does. I hope hoedown accepts this as well.
-
由 Pascal Hertleif 提交于
- Headlines begin at 1st level now like the rest of the book - All Headlines a blank line above and below - Fix links in this chapter's TOC
-
由 Andrea Canciani 提交于
Commit 9104a902 fixed the generated files, but that change would be lost (or require additional manual intervention) if they are re-generated of if new architectures are added. cc #28273
-
由 bors 提交于
Redirect stdout on the python bogosity detector. This is printing pwd to the terminal currently. Reformat the bogus python/cmake messages so they format correctly. echo does not always escape newlines (it doesn't here), and multiline strings don't whitespace munch. r? @alexcrichton
-
由 christopherdumas 提交于
-
由 bors 提交于
-
由 Brian Anderson 提交于
Redirect stdout on the python bogosity detector. This is printing pwd to the terminal currently. Reformat the bogus python/cmake messages so they format correctly. echo does not always escape newlines (it doesn't here), and multiline strings don't whitespace munch.
-
由 bors 提交于
This commit does some refactoring to make almost all of the `std::rt` private. Specifically, the following items are no longer part of its API: * DEFAULT_ERROR_CODE * backtrace * unwind * args * at_exit * cleanup * heap (this is just alloc::heap) * min_stack * util The module is now tagged as `#[doc(hidden)]` as the only purpose it's serve is an entry point for the `panic!` macro via the `begin_unwind` and `begin_unwind_fmt` reexports.
-
由 Alex Crichton 提交于
This commit does some refactoring to make almost all of the `std::rt` private. Specifically, the following items are no longer part of its API: * DEFAULT_ERROR_CODE * backtrace * unwind * args * at_exit * cleanup * heap (this is just alloc::heap) * min_stack * util The module is now tagged as `#[doc(hidden)]` as the only purpose it's serve is an entry point for the `panic!` macro via the `begin_unwind` and `begin_unwind_fmt` reexports.
-
由 bors 提交于
Noticed these yesterday while reading libsyntax
-
- 11 9月, 2015 20 次提交
-
-
由 Björn Steinbrink 提交于
-
由 bors 提交于
When the inliner has to decided if it wants to inline a function A into an internal function B, it first checks whether it would be more profitable to inline B into its callees instead. This means that it has to analyze B, which involves checking the assumption cache. Building the assumption cache requires scanning the whole function, and because inlining currently clears the assumption cache, this scan happens again and again, getting even slower as the function grows from inlining. As inlining the huge find functions isn't really useful anyway, we can mark them as noinline, which skips the cost analysis and reduces compile times by as much as 70%. cc #28273
-
由 Björn Steinbrink 提交于
When the inliner has to decided if it wants to inline a function A into an internal function B, it first checks whether it would be more profitable to inline B into its callees instead. This means that it has to analyze B, which involves checking the assumption cache. Building the assumption cache requires scanning the whole function, and because inlining currently clears the assumption cache, this scan happens again and again, getting even slower as the function grows from inlining. As inlining the huge find functions isn't really useful anyway, we can mark them as noinline, which skips the cost analysis and reduces compile times by as much as 70%. cc #28273
-
由 bors 提交于
llvm seems to be having some trouble optimizing the iterator-based string comparsion method into some equivalent to memcmp. This explicitly calls out to the memcmp intrinisic in order to allow llvm to generate better code. In some manual benchmarking, this memcmp-based approach is 20 times faster than the iterator approach.
-
由 bors 提交于
r? @pnkfelix
-
由 Nick Cameron 提交于
-
由 Nick Cameron 提交于
-
由 Vadim Petrochenkov 提交于
-
由 bors 提交于
-
由 bors 提交于
r? @Manishearth
-
由 bors 提交于
Closes #17994.
-
由 Erick Tryzelaar 提交于
llvm seems to be having some trouble optimizing the iterator-based string comparsion method into some equivalent to memcmp. This explicitly calls out to the memcmp intrinisic in order to allow llvm to generate better code. In some manual benchmarking, this memcmp-based approach is 20 times faster than the iterator approach.
-
由 bors 提交于
under OpenBSD, it could be have present multiples versions of gcc compiler: - gcc-4.2 (with patchs) : c/c++ compiler present in `/usr/bin`. It is unusable to build recent LLVM (so rustc too). - gcc/g++ -4.9 : c/c++ compiler, installed as third-party with "ports" mechanism. The compiler is installed in `/usr/local` as `egcc` (and `eg++`). this PR adds probing for `egcc` for `CFG_GCC`, if the first probed `gcc` is too old. It will set `CC` and `CXX` too, in order to pass the variables to LLVM configure if builded. please note this PR is a first step in order to build rustc under OpenBSD with unpatched tree. r? @alexcrichton cc @brson @dhuseby
-
由 bors 提交于
Fixes #27616. r? @pnkfelix
-
由 Andrew Paseltiner 提交于
Closes #17994.
-
由 bors 提交于
This was @steveklabnik's idea. Thanks @BurntSushi for the awesome blog post! r? @steveklabnik
-
由 bors 提交于
Fix the following error when running configure with llvm 3.8svn: configure: error: bad LLVM version: 3.8.0svn, need >=3.5
-
由 Sébastien Marie 提交于
depending of the compiler used, jemalloc configure don't detect correctly some parameters.
-
由 christopherdumas 提交于
-
由 bors 提交于
Closes #22638. Closes #22872. Closes #23024. Closes #23046.
-
- 10 9月, 2015 1 次提交
-
-
由 Andrew Paseltiner 提交于
Closes #22638. Closes #22872. Closes #23024. Closes #23046.
-