-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 7 pull requests #118248
Rollup of 7 pull requests #118248
Conversation
This will allow users to use rustc span messages to display user friendly messages.
Utilize a smart hash for 'llvm-finished-building' to enable recompilation of LLVM with each change in the git sources. Each change generates a unique hash value in 'llvm-finished-building', which ensures LLVM compilations only triggered with further changes. Signed-off-by: onur-ozkan <work@onurozkan.dev>
…es, r=clubby789 Recompile LLVM when it changes in the git sources Utilize a smart hash for 'llvm-finished-building' to enable recompilation of LLVM with each change in the git sources. Each change generates a unique hash value in 'llvm-finished-building', which ensures LLVM compilations only triggered with further changes. Resolves rust-lang#111893 cc `@rust-lang/wg-llvm`
…wu, r=compiler-errors intercrate ambiguity causes: ignore candidates which don't apply r? `@compiler-errors`
Add common trait for crate definitions In stable mir, we specialize DefId, however some functionality is the same for every definition, such as def paths, and getting their crate. Use a trait to implement those.
memcpy assumptions: update GCC link GCC now has this documented on an official website, not just in the bugtracker.
EvalCtxt::commit_if_ok don't inherit nested goals we use it to check whether an alias is rigid, so we want to avoid considering an alias rigid simply because the inference constraints from normalizing it caused another nested goal fail r? `@compiler-errors`
…, r=compiler-errors Add `Span` to `TraitBoundModifier` This improves diagnostics for the message "`~const` is not allowed here", and also fixes the span that we use when desugaring `~const Tr` into `Tr<host>` in effects desugaring.
…ler-errors Remove a hack for effects Fallback was implemented in rust-lang#115727, which addresses the inference errors mentioned in the comments.
@bors r+ rollup=never p=7 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 4fd68eb47b In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (42ae1a7): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 677.24s -> 676.964s (-0.04%) |
Successful merges:
Span
toTraitBoundModifier
#118245 (AddSpan
toTraitBoundModifier
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup