https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.85.0 2024-12-15T01:38:46+00:00 2024-12-15T01:38:46+00:00 jyn github@jyn.dev 2023-12-25T00:49:23+00:00 urn:sha1:a4ef751e26a90dd3b6b35fdbfef1e4854f9d80e1 the linker arguments can be *very* long, especially for crates with many dependencies. some parts of them are not very useful. unless specifically requested: - omit object files specific to the current invocation - fold rlib files into a single braced argument (in shell expansion format) this shortens the output significantly without removing too much information. 2024-11-15T14:25:19+00:00 Sven Kanoldt sven+oss@d34dl0ck.me 2024-10-09T12:24:15+00:00 urn:sha1:1696f534abe0655ee43ed57972a62d1cce42c233 - Add test for issue 47446 - Implement the new lint lint_builtin_mixed_export_name_and_no_mangle - Add suggestion how to fix it 2024-11-05T22:43:56+00:00 Matthias Krüger matthias.krueger@famsik.de 2024-11-05T22:43:56+00:00 urn:sha1:8dee3e978a712bf6ed377473352edfc13f5e235c bootstrap/codegen_ssa: ship llvm-strip and use it for -Cstrip Fixes #131206. - Includes `llvm-strip` (a symlink to `llvm-objcopy`) in the compiler dist artifact so that it can be used for `-Cstrip` instead of the system tooling. - Uses `llvm-strip` instead of `/usr/bin/strip` for macOS. macOS needs a specific linker and the system one is preferred, hence #130781 but that doesn't work when cross-compiling, so use the `llvm-strip` utility instead. cc #123151 2024-11-05T16:25:45+00:00 bors bors@rust-lang.org 2024-11-05T16:25:45+00:00 urn:sha1:e8c698bb3bdc121ac7f65919bd16d22f6567a3f1 mark some target features as 'forbidden' so they cannot be (un)set with -Ctarget-feature The context for this is https://github.com/rust-lang/rust/issues/116344: some target features change the way floats are passed between functions. Changing those target features is unsound as code compiled for the same target may now use different ABIs. So this introduces a new concept of "forbidden" target features (on top of the existing "stable " and "unstable" categories), and makes it a hard error to (un)set such a target feature. For now, the x86 and ARM feature `soft-float` is on that list. We'll have to make some effort to collect more relevant features, and similar features from other targets, but that can happen after the basic infrastructure for this landed. (These features are being collected in https://github.com/rust-lang/rust/issues/131799.) I've made this a warning for now to give people some time to speak up if this would break something. MCP: https://github.com/rust-lang/compiler-team/issues/780 2024-11-05T11:49:37+00:00 David Wood david.wood2@arm.com 2024-10-08T14:20:02+00:00 urn:sha1:f745467cd99cdcb62151c3b0c90f5467e7adfe69 2024-11-04T21:56:47+00:00 Ralf Jung post@ralfj.de 2024-09-02T09:45:59+00:00 urn:sha1:ffad9aac27ff8a78f5d751bf88250470e2e9d790 For now, this is just a warning, but should become a hard error in the future 2024-11-01T16:07:19+00:00 Mads Marquart mads@marquart.dk 2024-09-29T20:14:55+00:00 urn:sha1:1ef1af1c607fe268b5622041ff586ca603b8ec8d 2024-10-10T20:00:45+00:00 Matthias Krüger matthias.krueger@famsik.de 2024-10-10T20:00:45+00:00 urn:sha1:13976f1f25ac64d53a2e1317153f4cfb1324b351 codegen_ssa: consolidate tied target checks Fixes #105110. Fixes #105111. `rustc_codegen_llvm` and `rustc_codegen_gcc` duplicated logic for checking if tied target features were partially enabled. This PR consolidates these checks into `rustc_codegen_ssa` in the `codegen_fn_attrs` query, which also is run pre-monomorphisation for each function, which ensures that this check is run for unused functions, as would be expected. Also adds a test confirming that enabling one tied feature doesn't imply another - the appropriate error for this was already being emitted. I did a bisect and narrowed it down to two patches it was likely to be - something in #128796, probably #128221 or #128679. 2024-10-04T12:06:48+00:00 Urgau urgau@numericable.fr 2024-10-03T13:05:23+00:00 urn:sha1:018ba0528fa5d22712397e520351295f8582a525 2024-09-24T14:48:49+00:00 David Wood david.wood2@arm.com 2024-09-11T12:57:12+00:00 urn:sha1:207bc77e15acc9444bf6c3e74fa46607490a8e8a `rustc_codegen_llvm` and `rustc_codegen_gcc` duplicated logic for checking if tied target features were partially enabled. This commit consolidates these checks into `rustc_codegen_ssa` in the `codegen_fn_attrs` query, which also is run pre-monomorphisation for each function, which ensures that this check is run for unused functions, as would be expected.