- 04 2月, 2016 5 次提交
-
-
由 bors 提交于
Rust currently emits atomic loads and stores with the LLVM `volatile` qualifier. This is unnecessary and prevents LLVM from performing optimization on these atomic operations.
-
由 bors 提交于
Fixes #30349
-
由 bors 提交于
This pull request adds support for [Illumos](http://illumos.org/)-based operating systems: SmartOS, OpenIndiana, and others. For now it's x86-64 only, as I'm not sure if 32-bit installations are widespread. This PR is based on #28589 by @potatosalad, and also closes #21000, #25845, and #25846. Required changes in libc are already merged: https://github.com/rust-lang-nursery/libc/pull/138 Here's a snapshot required to build a stage0 compiler: https://s3-eu-west-1.amazonaws.com/nbaksalyar/rustc-sunos-snapshot.tar.gz It passes all checks from `make check`. There are some changes I'm not quite sure about, e.g. macro usage in `src/libstd/num/f64.rs` and `DirEntry` structure in `src/libstd/sys/unix/fs.rs`, so any comments on how to rewrite it better would be greatly appreciated. Also, LLVM configure script might need to be patched to build it successfully, or a pre-built libLLVM should be used. Some details can be found here: https://llvm.org/bugs/show_bug.cgi?id=25409 Thanks! r? @brson
-
由 bors 提交于
This is very useful when the RwLock is synchronizing access to a data structure and you would like to return or store guards which contain references to data inside the data structure instead of the data structure itself.
-
由 bors 提交于
This reports an error at the point of calling `Command::spawn()` or one of its equivalents. Fixes #30858 Fixes #30862
-
- 03 2月, 2016 31 次提交
-
-
由 Kamal Marhubi 提交于
This reports an error at the point of calling `Command::spawn()` or one of its equivalents. Fixes https://github.com/rust-lang/rust/issues/30858 Fixes https://github.com/rust-lang/rust/issues/30862
-
由 bors 提交于
r? @steveklabnik
-
由 Nikita Baksalyar 提交于
-
由 bors 提交于
I didn't change any content, just added another slash so we can see those comments in the docs r? @steveklabnik
-
由 Oliver Schneider 提交于
-
由 bors 提交于
-
由 bors 提交于
WIP implementation of #31209. The goal is to insert fake/dummy definitions for names that we failed to import so that later resolver stages won't complain about them.
-
由 bors 提交于
Something went haywire with github last night and the old PR https://github.com/rust-lang/rust/pull/31230 got closed somehow. This new PR is to replace the old one. This incorporates all of the feedback from the other PR. @alexcrichton I incorporated the suggestion from @semarie and the result is cleaner and clearer. I think this is ready to go.
-
由 Dave Huseby 提交于
-
由 Dave Huseby 提交于
-
由 Dave Huseby 提交于
-
由 Dave Huseby 提交于
-
由 Dave Huseby 提交于
-
由 Dirk Gadsden 提交于
-
由 Dirk Gadsden 提交于
-
由 bors 提交于
This mirrors the behavior of `clang-cl.exe` by adding a `CodeView` global variable when emitting debug information. This should in turn help stack traces that are generated when code is compiled with debuginfo enabled. Closes #28133
-
由 bors 提交于
- Successful merges: #27499, #31220, #31329, #31332, #31347, #31351, #31352, #31366 - Failed merges:
-
由 Jonathan Reem 提交于
-
由 Simonas Kazlauskas 提交于
-
由 Andrew Paseltiner 提交于
-
由 Manish Goregaokar 提交于
The context of the link is `Result` but it points to the docs on `Option`'s `expect`.
-
由 Manish Goregaokar 提交于
Fixes #31154
-
由 Manish Goregaokar 提交于
This is a behavior that some find confusing, so it deserves its own example. Fixes #31318 I think this wording might be a bit strange, but I couldn't come up with anything better. Feedback very welcome.
-
由 Manish Goregaokar 提交于
r? @EddyB
-
由 Manish Goregaokar 提交于
Small modification to #31288. Shows full path and line number for unused error codes.
-
由 Manish Goregaokar 提交于
Fixes #31098 AFAICT this is the only place where rustdoc explicitly checks if we are on stable before emitting content, so I can't tell if this is the sane way to handle this, or if anything else should be done to make sure that nobody forgets to remove this check when `const` is stabilized.
-
由 Manish Goregaokar 提交于
Fixes #30632 I'm not sure if this explanation is good enough. If it is, I will add it to filter as well.
-
由 Manish Goregaokar 提交于
Any documentation comments that contain raw-string-looking sequences may pretty-print invalid code when expanding them, as the current logic always uses the `r"literal"` form, without appending any `#`s. This commit calculates the minimum number of `#`s required to wrap a comment correctly and appends `#`s appropriately. Fixes #27489.
-
由 bors 提交于
Currently the `mipsel-unknown-linux-gnu` target doesn't actually set the `target_arch` value to `mipsel` but it rather uses `mips`. Alternatively the `powerpc64le` target does indeed set the `target_arch` as `powerpc64le`, causing a bit of inconsistency between theset two. As these are just the same instance of one instruction set, let's use `target_endian` to switch between them and only set the `target_arch` as one value. This should cut down on the number of `#[cfg]` annotations necessary and all around be a little more ergonomic.
-
由 Steve Klabnik 提交于
-
- 02 2月, 2016 4 次提交
-
-
由 Paul Smith 提交于
The context of the link is `Result` but it points to the docs on `Option`'s `expect`.
-
由 bors 提交于
Pretty printing of macro with braces but without terminated semicolon removed more boxes from stack than it put there, resulting in panic. This fixes the issue #30731.
-
由 bors 提交于
Using the test @bluss suggested in #30983
-
由 bors 提交于
- Successful merges: #30971, #31202, #31247, #31270, #31281, #31327, #31339, #31340, #31342, #31344, #31345, #31346, #31348 - Failed merges:
-