https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.87.0 2025-03-26T08:40:27+00:00 2025-03-26T08:40:27+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-03-26T08:40:27+00:00 urn:sha1:7eb27a9cf93f2c21626da278edab1235564d097c Target modifiers fix for bool flags without value Fixed support of boolean flags without values: `-Zbool-flag` is now consistent with `-Zbool-flag=true` in another crate. When flag is explicitly set to default value, target modifier will not be set in crate metainfo (`-Zflag=false` when `false` is a default value for the flag). Improved error notification when target modifier flag is absent in a crate ("-Zflag unset"). Example: ``` note: `-Zreg-struct-return=true` in this crate is incompatible with unset `-Zreg-struct-return` in dependency `default_reg_struct_return` ``` 2025-03-26T00:06:46+00:00 bors bors@rust-lang.org 2025-03-26T00:06:46+00:00 urn:sha1:068609ce766e55d2e7371cd2a86143a6d7e8e2e4 add FCW to warn about wasm ABI transition See https://github.com/rust-lang/rust/issues/122532 for context: the "C" ABI on wasm32-unk-unk will change. The goal of this lint is to warn about any function definition and calls whose behavior will be affected by the change. My understanding is the following: - scalar arguments are fine - including 128 bit types, they get passed as two `i64` arguments in both ABIs - `repr(C)` structs (recursively) wrapping a single scalar argument are fine (unless they have extra padding due to over-alignment attributes) - all return values are fine `@bjorn3` `@alexcrichton` `@Manishearth` is that correct? I am making this a "show up in future compat reports" lint to maximize the chances people become aware of this. OTOH this likely means warnings for most users of Diplomat so maybe we shouldn't do this? IIUC, wasm-bindgen should be unaffected by this lint as they only pass scalar types as arguments. Tracking issue: https://github.com/rust-lang/rust/issues/138762 Transition plan blog post: https://github.com/rust-lang/blog.rust-lang.org/pull/1531 try-job: dist-various-2 2025-03-25T07:22:35+00:00 Ralf Jung post@ralfj.de 2025-03-17T21:59:56+00:00 urn:sha1:072ccce553dd83ebfdf0aaf99eb24f65133c368b 2025-03-19T19:12:37+00:00 Camille GILLOT gillot.camille@gmail.com 2023-03-12T10:56:20+00:00 urn:sha1:5a21f890e9b6aad452638a45e0ebce025da7334f 2025-03-19T15:51:54+00:00 bors bors@rust-lang.org 2025-03-19T15:51:54+00:00 urn:sha1:1aeb99d248e1b0069110cb03c6f1dcc7b36fd7f3 Represent diagnostic side effects as dep nodes This changes diagnostic to be tracked as a special dep node (`SideEffect`) instead of having a list of side effects associated with each dep node. `SideEffect` is always red and when forced, it emits the diagnostic and marks itself green. Each emitted diagnostic generates a new `SideEffect` with an unique dep node index. Some implications of this: - Diagnostic may now be emitted more than once as they can be emitted once when the `SideEffect` gets marked green and again if the task it depends on needs to be re-executed due to another node being red. It relies on deduplicating of diagnostics to avoid that. - Anon tasks which emits diagnostics will no longer *incorrectly* be merged with other anon tasks. - Reusing a CGU will now emit diagnostics from the task generating it. 2025-03-17T15:42:23+00:00 bit-aloo sshourya17@gmail.com 2025-03-17T15:42:23+00:00 urn:sha1:4579615b14a3a2ee1a0040365d969d9526ed7e1c 2025-03-17T05:49:34+00:00 Andrew Zhogin andrew.zhogin@gmail.com 2025-03-06T22:34:12+00:00 urn:sha1:6ccaea19895cc8c0861f3a8707f888a15f8be3a1 2025-03-14T17:39:27+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2025-03-14T17:36:30+00:00 urn:sha1:453b51a65ab00939d2dce3de24ce38489b5c7eb6 2025-03-12T15:05:24+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-03-07T15:55:28+00:00 urn:sha1:b54398e4ea9188b0ccf60105e15ea5f2ed723edd build_session_options always uses materialize_sysroot anyway. 2025-02-22T13:32:44+00:00 bors bors@rust-lang.org 2025-02-22T13:32:44+00:00 urn:sha1:15469f8f8ae0a77577745cf56d562600fdb6539a Rollup of 9 pull requests Successful merges: - #136910 (Implement feature `isolate_most_least_significant_one` for integer types) - #137183 (Prune dead regionck code) - #137333 (Use `edition = "2024"` in the compiler (redux)) - #137356 (Ferris 🦀 Identifier naming conventions) - #137362 (Add build step log for `run-make-support`) - #137377 (Always allow reusing cratenum in CrateLoader::load) - #137388 (Fix(lib/fs/tests): Disable rename POSIX semantics FS tests under Windows 7) - #137410 (Use StableHasher + Hash64 for dep_tracking_hash) - #137413 (jubilee cleared out the review queue) r? `@ghost` `@rustbot` modify labels: rollup