- 13 6月, 2019 31 次提交
-
-
由 bors 提交于
ci: Enable toolstate tracking on Azure Currently just run it through its paces but don't actually push to official locations. Instead let's just push to a separate fork (mine) as well as open issues in a separate fork (mine). Make sure that people aren't pinged for these issues as well! This should hopefully ensure that everything is working on Azure and give us a chance to work through any issues that come up. Fixes https://github.com/rust-lang/rust/issues/61790 Fixes https://github.com/rust-lang/rust/issues/61371
-
由 Alex Crichton 提交于
Currently just run it through its paces but don't actually push to official locations. Instead let's just push to a separate fork (mine) as well as open issues in a separate fork (mine). Make sure that people aren't pinged for these issues as well! This should hopefully ensure that everything is working on Azure and give us a chance to work through any issues that come up.
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #61598 (Handle index out of bound errors during const eval without panic) - #61720 (std: Remove internal definitions of `cfg_if!` macro) - #61757 (Deprecate ONCE_INIT in future 1.38 release) - #61766 (submodules: update clippy from c0dbd34b to bd33a97c) - #61791 (Small cleanup in `check_pat_path`) Failed merges: r? @ghost
-
由 Mazdak Farrokhzad 提交于
Small cleanup in `check_pat_path`
-
由 Mazdak Farrokhzad 提交于
submodules: update clippy from c0dbd34b to bd33a97c Changes: ```` Fix implicit_return docs rustup https://github.com/rust-lang/rust/pull/61758/files Remove wrong lifetime from LintContext Workaround for rust-lang/rustfmt#3615 Fixing eta with respect to lazy evaluation. ```` r? @oli-obk
-
由 Mazdak Farrokhzad 提交于
Deprecate ONCE_INIT in future 1.38 release Once::new() has been a stable const fn for a while now. Closes #61746
-
由 Mazdak Farrokhzad 提交于
std: Remove internal definitions of `cfg_if!` macro This is duplicated in a few locations throughout the sysroot to work around issues with not exporting a macro in libstd but still wanting it available to sysroot crates to define blocks. Nowadays though we can simply depend on the `cfg-if` crate on crates.io, allowing us to use it from there!
-
由 Mazdak Farrokhzad 提交于
Handle index out of bound errors during const eval without panic Fix #61595
-
由 bors 提交于
update miri Fixes https://github.com/rust-lang/rust/issues/61662 r? @oli-obk
-
由 Ralf Jung 提交于
-
由 Matthias Krüger 提交于
Changes: ```` Fix wrong lifetime of TyCtxt travis: Wait at most 30 minutes for base test Typos and minor grammar corrections Adds lint for integer division redundant_closure_for_method_calls fixes: lint does not trigger when there is a difference in mutability lint does not trigger when the method belongs to a trait which is not implemebted directly (Deref) Fix implicit_return docs rustup https://github.com/rust-lang/rust/pull/61758/files Remove wrong lifetime from LintContext Workaround for rust-lang/rustfmt#3615 Fixing eta with respect to lazy evaluation. ````
-
由 Steven Fackler 提交于
Once::new() has been a stable const fn for a while now. Closes #61746
-
由 bors 提交于
Bump dirs, rand and redox_users Part of #57724.
-
由 Mazdak Farrokhzad 提交于
-
由 bors 提交于
Rollup of 9 pull requests Successful merges: - #60376 (Stabilize Option::xor) - #61398 (Stabilize copy_within) - #61629 (Hygienize macros in the standard library) - #61675 (Include frame pointer for bare metal RISC-V targets) - #61750 (Fix x.py install) - #61761 (Add an alias for x86_64-sun-solaris target tuple) - #61762 (rustbuild: fix libtest_stamp) - #61763 (ci: fix ci stats upload condition) - #61776 (Fix typos in error_codes) Failed merges: r? @ghost
-
由 Mazdak Farrokhzad 提交于
Fix typos in error_codes `observedin` should be `observed in`.
-
由 Mazdak Farrokhzad 提交于
ci: fix ci stats upload condition The condition I suggested in #61632 was not correct and it errors out while evaluating. This fixes the condition. [Example of a failure](https://dev.azure.com/rust-lang/rust/_build/results?buildId=543). r? @alexcrichton
-
由 Mazdak Farrokhzad 提交于
rustbuild: fix libtest_stamp Looks like an obvious copy/paste typo
-
由 Mazdak Farrokhzad 提交于
Add an alias for x86_64-sun-solaris target tuple Closes #40531 r? @varkor
-
由 Mazdak Farrokhzad 提交于
Fix x.py install Make sure we look for save analysis in the right place. Fixes #61703. r? @Mark-Simulacrum cc @petrhosek @cramertj
-
由 Mazdak Farrokhzad 提交于
Include frame pointer for bare metal RISC-V targets This changes the default setting to enable the use of the frame pointer register when targeting RISC-V. On that architecture there is a dedicated frame pointer register which LLVM would otherwise never use so there is no increase in register pressure. Further, since these are bare metal targets, getting backtraces without the frame pointer is considerably more difficult (you can't just ask the OS to load the ELF executable and parse DWARF symbols). It is true that this setting can also be changed with the `-C force-frame-pointers` flag but that won't impact the compilation of the standard library, meaning that backtraces from, say, a panic handler would be useless.
-
由 Mazdak Farrokhzad 提交于
Hygienize macros in the standard library Same as https://github.com/rust-lang/rust/pull/55597, but for all macros in the standard library. Nested macro calls will now call what they are intended to call rather than whatever is in the closest scope at call site. Technically this is a breaking change, so crater run would probably be useful. --- One exception that is not hygienized is calls to `panic!(...)`. Macros defined in libcore do not want to call `core::panic`. What they really want to call is either `std::panic` or `core::panic` depending on `no_std` settings. EDIT: After some thought, recursive calls to `panic` from `panic` itself probably do want to use `$crate` (UPDATE: done). Calling `std::panic` from macros defined in std and "whatever `panic` is in scope" from macros defined in libcore is probably even worse than always calling "whatever `panic` is in scope", so I kept the existing code. The only way to do the std/core switch correctly that I'm aware of is to define a built-in panic macro that would dispatch to `std::panic` or `core::panic` using compiler magic. Then standard library macros could delegate to this built-in macro. The macro could be named `panic` too, that would fix https://github.com/rust-lang/rust/issues/61567. (This PR doesn't do that.) --- cc https://github.com/rust-lang/rust/issues/56389 cc https://github.com/rust-lang/rust/issues/61567 Fixes https://github.com/rust-lang/rust/issues/61699 r? @alexcrichton
-
由 Mazdak Farrokhzad 提交于
Stabilize copy_within Closes #54236.
-
由 Mazdak Farrokhzad 提交于
Stabilize Option::xor FCP done in https://github.com/rust-lang/rust/issues/50512#issuecomment-469527554 . Closes #50512 .
-
由 Esteban Küber 提交于
-
由 bors 提交于
Use a single lifetime for MIR construction Builds on https://github.com/rust-lang/rust/pull/57214 r? @EddyB
-
由 Lzu Tao 提交于
-
由 Vadim Petrochenkov 提交于
-
由 John Kåre Alsaker 提交于
-
由 Laurențiu Nicola 提交于
-
由 bors 提交于
Special-case literals in `parse_bottom_expr`. This makes parsing faster, particularly for code with large constants, for two reasons: - it skips all the keyword comparisons for literals; - it skips the allocation done by the `mk_expr` call in `parse_literal_maybe_minus`. r? @petrochenkov
-
- 12 6月, 2019 9 次提交
-
-
由 Yuki Okushi 提交于
-
由 bors 提交于
rustc: replace `TyCtxt<'a, 'gcx, 'tcx>` with `TyCtxt<'gcx, 'tcx>`. This first lifetime parameter of `TyCtxt` has been phantom for a while, thanks to @Zoxc, but was never removed, and I'm doing this now in preparation for removing the `'gcx`/`'tcx` split. I wasn't going to do this as a separate step, and instead start converting uses of `TyCtxt` to a single-lifetime alias of it (e.g. `type TyCx<'tcx> = TyCtxt<'tcx, 'tcx, 'tcx>;`) but it turns out (as @Zoxc rightly predicted) that there is far more fallout from not needing a lifetime for the first parameter of `TyCtxt`. That is, going from `TyCtxt<'a, 'gcx, 'tcx>` to `TyCtxt<'tcx, 'gcx, 'tcx>` (the first commit in this PR) has the largest amount of fallout out of all the changes we might make (because it can require removing the `'a` parameter of `struct`s containing `tcx: TyCtxt<'a, ...>`), and is the hardest to automate (because `'a` is used everywhere, not just with `TyCtxt`, unlike, say `'gcx, 'tcx` -> `'tcx`). So I'm submitting this now to get it out of the way and reduce further friction in the future. **EDIT**: for the `rustfmt` commit, I used https://github.com/rust-lang/rustfmt/issues/1324#issuecomment-482109952, and manually filtered out some noise, like in #61735, but unlike that PR, there was also a weird bug to work around. It should be reviewed separately, and dropped if unwanted. cc @rust-lang/compiler r? @nikomatsakis
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Pietro Albini 提交于
The condition I suggested in #61632 was not correct and it errors out while evaluating. This fixes the condition. Example of a failure: https://dev.azure.com/rust-lang/rust/_build/results?buildId=543
-
由 bors 提交于
ci: Disable LLVM/debug assertions for distcheck The purpose of distcheck is to test `./x.py test` from a tarball, not to test that all assertions pass all the time. These assertions are largely just redundant with other builders, so skip the assertions for now and save a good chunk of time on CI. cc #61185
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-