- 08 6月, 2020 6 次提交
-
-
由 Ayush Kumar Mishra 提交于
-
由 bors 提交于
save_analysis: fix some ICEs Fixes #73020 Fixes #73022 Fixes #73041
-
由 bors 提交于
Order the Rust and C ABIs first to reduce test churn
-
由 Dylan DPC 提交于
Fix codegen tests for RISC-V Some codegen tests didn't seem relevant (e.g. unsupported annotations). The RISC-V abi tests were broken by LLVM 10, c872dcf9 fixes that (cc: @msizanoen1) I'm not sure about skipping catch-unwind.rs and included that change here mostly as a request for comment - I can't tell if that's a bug.
-
由 Dylan DPC 提交于
run-make regression test for issue #70924. Sometime after my PR #72767 (to fix issue #70924) landed, I realized that I *could* make a local regression test, thanks to `rustc --print sysroot`: I can make a fresh "copy" (really mostly symlinks) of the sysroot, and then modify it to recreate the terms of this bug.
-
- 07 6月, 2020 21 次提交
-
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #72764 (Be more careful around ty::Error in generators) - #72908 (rename FalseEdges -> FalseEdge) - #72970 (Properly handle feature-gated lints) - #72998 (Mention that some atomic operations may not be available on some platforms) - #73063 (Elide type on liballoc vec) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
Elide type on liballoc vec
-
由 Dylan DPC 提交于
Mention that some atomic operations may not be available on some platforms fixes #54250 This simply adds a line saying the type/function/method may not be available on some platforms, depending on said platform capabilities. I *think* I got them all.
-
由 Dylan DPC 提交于
Properly handle feature-gated lints Closes #72694
-
由 Dylan DPC 提交于
rename FalseEdges -> FalseEdge There's just a single false edge in this terminator, not multiple of them. r? @matthewjasper @jonas-schievink
-
由 Dylan DPC 提交于
Be more careful around ty::Error in generators cc https://github.com/rust-lang/rust/issues/72685 (doesn't close it because it's missing a reproduction to use as a test case) r? @estebank
-
由 Ralf Jung 提交于
-
由 bors 提交于
Update LLVM submodule to include lld NOLOAD fix > Rust nightly 2020-05-22 and later ships lld with a regression related to linker scripts: NOLOAD sections incorrectly generate sections filled with 0s. This causes gdb and other elf loaders to write to reserved or otherwise invalid addresses (gdb also seems confused by the resulting ELF files and spits out a warning about the sections). This is particularly a problem for embedded rust projects that use lld by default and have affected linker scripts (cortex-m-rt based projects for instance). https://github.com/rust-lang/llvm-project/pull/64 Note that this also pulls in llvm changes from #72937
-
由 Jake Goulding 提交于
-
由 Dylan DPC 提交于
remove outdated comment r? @matthewjasper
-
由 Dylan DPC 提交于
Clean up E0644 explanation r? @Dylan-DPC
-
由 Dylan DPC 提交于
Count the beta prerelease number just from master We were computing a merge-base between the remote beta and master branches, but this was giving incorrect answers for the first beta if the remote hadn't been pushed yet. For instance, `1.45.0-beta.3359` corresponds to the number of merges since the 1.44 beta, but we really want just `.1` for the sole 1.45 beta promotion merge. We don't really need to query the remote beta at all -- `master..HEAD` suffices if we assume that we're on the intended beta branch already.
-
由 Dylan DPC 提交于
Revert pr 71840 Revert7 PR #71840 to fix issue #72470 This will need a backport to beta if we do not want #72470 to hit stable.
-
由 Dylan DPC 提交于
validate basic sanity for TerminatorKind r? @jonas-schievink This mainly checks that all `BasicBlock` actually exist. On top of that, it checks that `Call` actually calls something of `FnPtr`/`FnDef` type, and `Assert` has to work on a `bool`. Also `SwitchInt` cannot have an empty target list.
-
由 marmeladema 提交于
-
由 Poliorcetics 提交于
Co-authored-by: NAmanieu d'Antras <amanieu@gmail.com>
-
由 Ralf Jung 提交于
linker: Add a linker rerun hack for gcc versions not supporting -static-pie Which mirrors the existing `-no-pie` linker rerun hack, but the logic is a bit more elaborated in this case. If the linker (gcc or clang) errors on `-static-pie` we rerun in with `-static` instead. We must also replace CRT objects corresponding to `-static-pie` with ones corresponding to `-static` in this case. (One sanity check for CRT objects in target specs is also added as a drive-by fix.) To do in the future: refactor all linker rerun hacks into separate functions and share more code with `add_(pre,post)_link_objects`. This PR accompanies https://github.com/rust-lang/rust/pull/71804 and unblocks https://github.com/rust-lang/rust/pull/70740.
-
由 Ralf Jung 提交于
Make `PolyTraitRef::self_ty` return `Binder<Ty>` This came up during review of #71618. The current implementation is the same as a call to `skip_binder` but harder to audit. Make it preserve binding levels and add a call to `skip_binder` at all use sites so they can be audited as part of #72507.
-
由 Ralf Jung 提交于
de-promote Duration::from_secs In https://github.com/rust-lang/rust/pull/67531, we removed the `rustc_promotable` attribute from a bunch of `Duration` methods, but not from `Duration::from_secs`. This makes the current list of promotable functions the following (courtesy of @ecstatic-morse): * `INT::min_value`, `INT::max_value` * `std::mem::size_of`, `std::mem::align_of` * `RangeInclusive::new` (backing `x..=y`) * `std::ptr::null`, `std::ptr::null_mut` * `RawWaker::new`, `RawWakerVTable::new` ??? * `Duration::from_secs` I feel like the last one stands out a bit here -- the rest are all very core language primitives, and `RawWaker` has a strong motivation for getting a `'static` vtable. But a `&'static Duration`? That seems unlikely. So I propose we no longer promote calls to `Duration::from_secs`, which is what this PR does. https://github.com/rust-lang/rust/pull/67531 saw zero regressions and I am not aware of anyone complaining that this broke their (non-cratered) code, so I consider it likely the same will be true here, but of course we'd do a crater run. See [this document](https://github.com/rust-lang/const-eval/blob/master/promotion.md) for some more background on promotion and https://github.com/rust-lang/const-eval/issues/19 for some of the concerns around promoting function calls.
-
- 06 6月, 2020 10 次提交
-
-
由 Ivan Tham 提交于
-
由 Bastian Kauschke 提交于
-
由 Guillaume Gomez 提交于
-
由 bors 提交于
Rename all remaining compiler crates to use the `rustc_foo` pattern libarena -> librustc_arena libfmt_macros -> librustc_parse_format libgraphviz -> librustc_graphviz libserialize -> librustc_serialize Closes https://github.com/rust-lang/rust/issues/71177 in particular.
-
由 marmeladema 提交于
-
由 Joey Hain 提交于
- lint: add `feature_gate` field, allow specifying it in `declare_lint!` - generalize the lint feature gate check - librustdoc: generalize whitelisting of feature-gated lints
-
由 bors 提交于
resolve: Sort E0408 errors by Symbol str This is a request for comments implementing my suggested solution to https://github.com/rust-lang/rust/issues/72913 Previously errors were sorted by Symbol index instead of the string. The indexes are not the same between architectures because Symbols for architecture extensions (e.g. x86 AVX or RISC-V d) are interned before the source file is parsed. RISC-V's naming of extensions after single letters led to it having errors sorted differently for test cases using single letter variable names. Instead sort the errors by the Symbol string so that it is stable across architectures. While I was at it, there's also 8edb05c2 skipping some ui tests which I think are irrelevant for risc-v.
-
-
由 Alexis Bourget 提交于
-
由 Felix S. Klock II 提交于
-
- 05 6月, 2020 3 次提交