| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
|
|
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
|
|
|
|
|
|
Do not run per-module late lints if they can be all skipped
We run ~70 late lints for all dependencies even if they use `--cap-lints=allow`, which seems wasteful. It looks like these lints are super fast (unlike early lints), but still.
r? `@ghost`
|
|
Mark `floor_char_boundary`, `ceil_char_boundary` const
Simplify the implementations, reducing the number of arithmetic operations
|
|
This reverts commit f877aa7d14916f71a2f88c6d4c009e7ded7684c4.
|
|
This config was added in 207de019dc67 ("libary: Forward
compiler-builtins "asm" and "mangled-names" feature") but it does not
appear this has ever been used. The PR adding it (RUST-78472) says that
this was exposed to help with configuration and points at the [Hermit
Cargo config], but as far as I can tell, this feature name has never
been mentioned in that repository's git history.
Thus, clean up a seemingly unneeded feature.
[Hermit Cargo config]: https://github.com/hermit-os/hermit-rs/blob/ab2b830930e6a9a98c8294997a8183feeabeda4a/.cargo/config
|
|
Naked functions are allowed to define global labels, just like
`global_asm!`.
|
|
|
|
Update cargo
8 commits in 6833aa715d724437dc1247d0166afe314ab6854e..9b296973b425ffb159e12cf3cd56580fd5c85382
2025-07-13 02:25:52 +0000 to 2025-07-25 17:10:08 +0000
- Allow using Cargo-as-a-library with gix's reqwest backend (rust-lang/cargo#15653)
- Make timings graphs scalable to user's window (rust-lang/cargo#15766)
- refactor: rename arg `mode` to `intent` (rust-lang/cargo#15774)
- fix: `no-proc-macro` is overridden by subsequent edges (rust-lang/cargo#15764)
- Use `gix` for `cargo package` (rust-lang/cargo#15534)
- cargo-credential-libsecret: give FFI correctly-sized object (rust-lang/cargo#15767)
- Remove unnecessary target-c-int-width from target specs (rust-lang/cargo#15759)
- Expose artifact dependency getters in cargo-as-a-library (rust-lang/cargo#15753)
|
|
|
|
LLVM codegen backend.
|
|
LLVM codegen backend.
|
|
This is PR: https://github.com/rust-lang/rustc-dev-guide/pull/2219
|
|
Let's revise both the new content in this PR as well as the remaining
text in the relevant chapters so as to better describe our current
processes related to language features and their stabilizations.
For the new stabilization report template, based on reviewing its
early use and well as reviewing earlier stabilization reports, we've
revised it editorially and added questions designed to capture
additional details to which we commonly want people to speak.
|
|
- Address Call for Testing review feedback
- Address Affiliated work review feedback
- Drop "stabilization is easy" part
- Fix broken feature gate examples
- Elaborate on stabilization report summarization aspects
- Recommend waiting a bit for team nominations
- Make Stabilization Template markdown copy friendly
- Register stabilization report template
- Drop unfinished sentence
- Clarify stabilization report template is for language features
- Add test coverage elaboration
- Add UB checks / opt question
- Amend test coverage explanation
- Mention OSS nightly users
|
|
Co-authored-by: lcnr <rust@lcnr.de>
Co-authored-by: Ralf Jung <post@ralfj.de>
Co-authored-by: waffle <waffle.lapkin@gmail.com>
|
|
|
|
if the expression cannot be evaluated in a straightforward way
|
|
This feature used to be for when Cranelift didn't support inline
assembly, but its last uses were removed in 52933e0bd200 ("Don't disable
inline asm usage in compiler-builtins when the cranelift backend is
enabled"). and cba05a7a14b3 ("Support naked functions").
This doesn't remove the feature from the `compiler-builtins` crate, that
will be done separately in the subtree repo.
|
|
Since rust-lang/rust be35d37d8b6c ("Use the compiler to determine
whether or not to enable f16 and f128"), `compiler-builtins` relies on
`rustc` to report whether or not `f16` and `f128` are supported, which
is reported by the backend. This means that there should no longer be
any need to unconditionally disable the types for clif in Bootstrap.
Backend config: https://github.com/rust-lang/rust/blob/a955f1cd09a027363729ceed919952d09f76f28e/compiler/rustc_codegen_cranelift/src/lib.rs#L224-L233
|
|
`intrinsic-test`: combine rust files for faster compilation
|
|
|
|
|
|
|
|
|
|
ring is brought into Cargo transitively because Cargo now
provides optional (unstable) reqwest HTTP backend.
|
|
|
|
changelog: none
|
|
|
|
|
|
|
|
|
|
|
|
there is no `llvm.lld` option
|
|
|
|
|
|
|
|
|
|
Clippy subtree update
r? `@Manishearth`
|
|
|
|
When encountering a moved value of a type that isn't `Clone` because of unmet obligations, but where all the unmet predicates reference crate-local types, mention them and suggest cloning, as we do in other cases already:
```
error[E0507]: cannot move out of `foo`, a captured variable in an `Fn` closure
--> f111.rs:14:25
|
13 | fn do_stuff(foo: Option<Foo>) {
| --- captured outer variable
14 | require_fn_trait(|| async {
| -- ^^^^^ `foo` is moved here
| |
| captured by this `Fn` closure
15 | if foo.map_or(false, |f| f.foo()) {
| ---
| |
| variable moved due to use in coroutine
| move occurs because `foo` has type `Option<Foo>`, which does not implement the `Copy` trait
|
note: if `Foo` implemented `Clone`, you could clone the value
--> f111.rs:4:1
|
4 | struct Foo;
| ^^^^^^^^^^ consider implementing `Clone` for this type
...
15 | if foo.map_or(false, |f| f.foo()) {
| --- you could clone this value
```
|
|
|
|
this makes the triagebot pings for this module simpler
|
|
|
|
Migrate `replace derive with manual impl` and `add_missing_impl_members` to use `SyntaxEditor`
|
|
|
|
|
|
|
