| Age | Commit message (Collapse) | Author | Lines |
|
Rollup of 3 pull requests
Successful merges:
- #118941 (llvm-wrapper: adapt for LLVM API changes)
- #119068 (Copy 1.74.1 release notes to master)
- #119080 (Comment out `change-id` in `config.example.toml`)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
|
|
cc rust-lang/rust#118540
Fixes rust-lang/rustc_codegen_cranelift#1435
|
|
|
|
cc rust-lang/rust#118538
|
|
r=Kobzol
Comment out `change-id` in `config.example.toml`
This way, we only update CONFIG_CHANGE_HISTORY for major changes, which is much simpler (and updating example.toml doesn't make much sense)
r? `@Kobzol` (as this was mainly your idea)
|
|
r=Mark-Simulacrum
Copy 1.74.1 release notes to master
- #119065
- this cherry-pick 1.74.1 release note from #118607(66033ec4e5762bc7d6b274938c294ac65e12161d)
Fixes #119065.
|
|
llvm-wrapper: adapt for LLVM API changes
Adapt for https://github.com/llvm/llvm-project/commit/8ecbb0404d740d1ab173554e47cef39cd5e3ef8c.
r? `@nikic`
`@rustbot` label: +llvm-main
|
|
Document unstable linker flags in the unstable book
This PR:
- removes the unstable linker flavors from the stable documentation
- documents the unstable `-C linker-flavor` values in the unstable book (including the ones previously described as stable)
- documents the unstable `-C link-self-contained` components in the unstable book
I don't know if these have some common reviewers, but if not r? `@petrochenkov` as the most knowledgeable person in this area. Please feel free to reassign, I know that you are quite busy.
|
|
This matches type_has_metadata in cg_ssa and doesn't require computing
the layout of the type. It is also a bit faster.
|
|
|
|
cc rust-lang/rust#118534
|
|
|
|
Fix ICE `ProjectionKinds Deref and Field were mismatched`
Fix #118144
Removed the check that ICEd if the sequence of projection kinds were different across captures. Instead we now sort based only on `Field` projection kinds.
|
|
This way, we only update CONFIG_CHANGE_HISTORY for major changes, which is
much simpler (and updating example.toml doesn't make much sense)
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
r=cjgillot
Properly reject `default` on free const items
Fixes #117791.
Technically speaking, this is a breaking change but I doubt it will lead to any real-world regressions (maybe in some macro-trickery crates?). Doing a crater run probably isn't worth it.
|
|
Adapt for https://github.com/llvm/llvm-project/commit/8ecbb0404d740d1ab173554e47cef39cd5e3ef8c.
|
|
|
|
Subtree update of `rust-analyzer`
|
|
This commit replaces this pattern:
```
err.into_diagnostic(dcx)
```
with this pattern:
```
dcx.create_err(err)
```
in a lot of places.
It's a little shorter, makes the error level explicit, avoids some
`IntoDiagnostic` imports, and is a necessary prerequisite for the next
commit which will add a `level` arg to `into_diagnostic`.
This requires adding `track_caller` on `create_err` to avoid mucking up
the output of `tests/ui/track-diagnostics/track4.rs`. It probably should
have been there already.
|
|
|
|
|
|
|
|
Rollup of 5 pull requests
Successful merges:
- #118852 (coverage: Skip instrumenting a function if no spans were extracted from MIR)
- #118905 ([AIX] Fix XCOFF metadata)
- #118967 (Add better ICE messages for some undescriptive panics)
- #119051 (Replace `FileAllocationInfo` with `FileEndOfFileInfo`)
- #119059 (Deny `~const` trait bounds in inherent impl headers)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
|
|
|
|
Deny `~const` trait bounds in inherent impl headers
Follow-up to #117817.
Implements https://github.com/rust-lang/rust/pull/117817#discussion_r1416213747.
Fixes #117004.
r? fee1-dead or compiler
|
|
Replace `FileAllocationInfo` with `FileEndOfFileInfo`
This fixes WINE support
|
|
Add better ICE messages for some undescriptive panics
Add some better messages at some panics
re: #118955
I took a look at some others but either was not able to figure out what they did, or it was unclear what they should say instead. For example in the query system whether each time a poisoned value is matched upon if they should all just call `FatalError.raise()`
|
|
[AIX] Fix XCOFF metadata
#118344 accidentally changed the way to get metadata from XCOFF file and broken our internal CI.
This PR reverts part of #118344 .
|
|
coverage: Skip instrumenting a function if no spans were extracted from MIR
The immediate symptoms of #118643 were fixed by #118666, but some users reported that their builds now encounter another coverage-related ICE:
```
error: internal compiler error: compiler/rustc_codegen_llvm/src/coverageinfo/mapgen.rs:98:17: A used function should have had coverage mapping data but did not: (...)
```
I was able to reproduce at least one cause of this error: if no relevant spans could be extracted from a function, but the function contains `CoverageKind::SpanMarker` statements, then codegen still thinks the function is instrumented and complains about the fact that it has no coverage spans.
This PR prevents that from happening in two ways:
- If we didn't extract any relevant spans from MIR, skip instrumenting the entire function and don't create a `FunctionCoverateInfo` for it.
- If coverage codegen sees a `CoverageKind::SpanMarker` statement, skip it early and avoid creating `func_coverage`.
---
Fixes #118850.
|
|
|
|
Consistent `Handler` naming
This PR implements the renaming described in https://github.com/rust-lang/compiler-team/issues/699.
r? `@compiler-errors`
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
`DiagnosticDeriveKind::Diagnostic::dcx`.
|
|
|
|
|
|
|
|
|
|
`UnstableOptions::dcx_flags`.
|