- 16 2月, 2016 11 次提交
-
-
由 bors 提交于
Part of https://github.com/rust-lang/rust/issues/31185. Similar to https://github.com/rust-lang/rust/pull/31391.
-
由 bors 提交于
This follows the pattern already used for stat functions from #31551. Now `ftruncate`, `lseek`, and `readdir_r` use their explicit 64-bit variants for LFS support, using wider `off_t` and `dirent` types. This also updates to `open64`, which uses no different types but implies the `O_LARGEFILE` flag. Non-Linux platforms just map their normal functions to the 64-bit names. r? @alexcrichton
-
由 bors 提交于
Fixes #31122.
-
由 bors 提交于
This enables `*` in all type positions in doc searches, which I often want in order to find functions that create or convert specific types (e.g. `* -> vec`) but I don't actually know what kinds of input they expect. I actually started working on this because of #31598, but I've wanted it several times when exploring new crates.
-
由 bors 提交于
- Successful merges: #31551, #31581, #31614, #31626, #31632, #31642 - Failed merges:
-
由 Johan Lorenzo 提交于
-
由 Dirk Gadsden 提交于
Closes #31554. Contributes to #29380.
-
由 Brandon W Maister 提交于
This enables `*` in all type positions in doc searches, which I often want in order to find functions that create or convert specific types (e.g. `* -> vec`) but I don't actually know what kinds of input they expect. I actually started working on this because of #31598, but I've wanted it several times when exploring new crates.
-
由 Keith Yeung 提交于
-
由 bors 提交于
Fixes #31497.
-
由 bors 提交于
-
- 15 2月, 2016 29 次提交
-
-
由 Corey Farwell 提交于
Part of https://github.com/rust-lang/rust/issues/31185. Similar to https://github.com/rust-lang/rust/pull/31391.
-
由 bors 提交于
This allows obtaining a textual MIR dump for individual items or all items in the crate. I haven't added any tests since ~~I'm too lazy~~ this is an unstable debugging option, but I'll add one if required. MIR for a single function can now be dumped using `rustc -Zunstable-options --unpretty mir=my_function` and no longer requires the use of in-source `#[rustc_mir]` attributes. Blocks rust-lang/rust-playpen#154 (if MIR dump support from the playpen is even wanted). Example output: ```rust fn main() { let x = Some(0); x.unwrap_or_else(|| 1); } ``` ``` MIR for expr || 1 (id=16) fn(arg0: [closure@test.rs:3:22: 3:26]) -> i32 { let mut tmp0: (); bb0: { return = const 1; goto -> bb1; } bb1: { return; } } MIR for fn main::main (id=4) fn() -> () { let var0: core::option::Option<i32>; // x let mut tmp0: (); let mut tmp1: i32; let mut tmp2: core::option::Option<i32>; let mut tmp3: [closure@test.rs:3:22: 3:26]; bb0: { var0 = core::option::Option::Some(const 0); tmp2 = var0; tmp3 = [closure@test.rs:3:22: 3:26]; tmp1 = core::option::Option<T>::unwrap_or_else(tmp2, tmp3) -> bb2; } bb1: { return; } bb2: { drop(tmp1) -> bb3; } bb3: { return = (); goto -> bb1; } } ```
-
由 bors 提交于
In other words, enforce what was documented in #30626 (and also stop blaming it on LLVM, we have at least one Python script of our own). Also, there is no Python later than 2.7 and there never will be.
-
由 bors 提交于
Needs a correct review because I'm not too confident with how this works. All tests related to the C ABI are now passing. References: - https://github.com/kripken/emscripten-fastcomp-clang/blob/dbe68fecd03d6f646bd075963c3cc0e7130e5767/lib/CodeGen/TargetInfo.cpp#L479-L489 - https://github.com/kripken/emscripten-fastcomp-clang/blob/dbe68fecd03d6f646bd075963c3cc0e7130e5767/lib/CodeGen/TargetInfo.cpp#L466-L477 The `classifyArgumentType` function has two different paths depending on `RAA == CGCXXABI::RAA_DirectInMemory`, but I don't really know what's the corresponding option in Rust. cc @brson @EddyB
-
由 bors 提交于
remove unused import that cause an error at compile-time. r? @alexcrichton
-
由 bors 提交于
This PR fixes two unrelated diagnostics bugs in resolve. First, it reports privacy errors for an import only after the import resolution is determined, fixing #31402. Second, it expands the per-module map from block ids to anonymous modules so that it also maps module declarations ids to modules, and it uses this map to in `with_scope` to fix #31644. r? @nrc
-
由 Dirk Gadsden 提交于
This is because the tool compiler passes the name of the tool as a command line `--cfg`. The improved session config parser is stricter and no longer permits invalid meta items (such as "error-index-generator").
-
由 Keith Yeung 提交于
-
由 bors 提交于
This fixes a regression caused by #31461 allowing extern crates to be glob imported, and it fixes the test that was supposed to catch it. r? @nrc
-
由 bors 提交于
Recover from missing brackets in the parser
-
由 Josh Stone 提交于
-
由 Josh Stone 提交于
-
由 Josh Stone 提交于
-
由 Josh Stone 提交于
-
由 Dirk Gadsden 提交于
Includes compile-fail test to check that it fails on incomplete `--cfg` matches. Fixes #31497.
-
由 Nick Cameron 提交于
-
由 NODA, Kai 提交于
It is no longer necessary after dd0d495fSigned-off-by: NNODA, Kai <nodakai@gmail.com>
-
由 bors 提交于
- Successful merges: #31607, #31649, #31655, #31658 - Failed merges:
-
由 Steve Klabnik 提交于
In the Rust code above this block of compiler output, the function is called print_sum, so use the same function name in the error message.
-
由 Steve Klabnik 提交于
r? @steveklabnik
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
Fixes #31599
-
由 bors 提交于
Looking at some profiles of rustc recently, these seemed like two pretty easy wins we could get in terms of performance on the table.
-
由 Nick Cameron 提交于
-
由 Nick Cameron 提交于
-
由 Nick Cameron 提交于
Some tests just add the extra errors, others I fix by doing some simple error recovery. I've tried to avoid doing too much in the hope of doing something more principled later. In general error messages are getting worse at this stage, but I think in the long run they will get better.
-
由 Nick Cameron 提交于
-
由 Nick Cameron 提交于
-
由 Alex Crichton 提交于
Now that we properly only link in jemalloc when building executables, we have far less to worry about in terms of polluting the global namespace with the `free` and `malloc` symbols on Linux. This commit will primarily allow LLVM to use jemalloc so the compiler will only be using one allocator overall. Locally this took compile time for libsyntax from 95 seconds to 89 (a 6% improvement).
-