about summary refs log tree commit diff
path: root/src/doc/rustc
AgeCommit message (Collapse)AuthorLines
2025-01-16Update docs for `-Clink-dead-code` to discourage its useZalathar-5/+5
2025-01-09Auto merge of #135268 - pietroalbini:pa-bump-stage0, r=Mark-Simulacrumbors-1/+1
Master bootstrap update Part of the release process. r? `@Mark-Simulacrum`
2025-01-08update version placeholdersPietro Albini-1/+1
2025-01-06Add new `{x86_64,i686}-win7-windows-gnu` targetsTobias Bucher-2/+57
These are in symmetry with `{x86_64,i686}-win7-windows-msvc`.
2025-01-06Escape all `*` in rustc's SUMMARY.mdTobias Bucher-9/+9
2025-01-06Auto merge of #135085 - knickish:m68k_unknown_none, r=workingjubileebors-0/+110
add m68k-unknown-none-elf target r? `@workingjubilee` The existing `m68k-unknown-linux-gnu` target builds `std` by default, requires atomics, and has a base cpu with an fpu. A smaller/more embedded target is desirable both to have a baseline target for the ISA, as well to make debugging easier for working on the llvm backend. Currently this target is using the `M68010` as the minimum CPU due, but as missing features are merged into the `M68k` llvm backend I am hoping to lower this further. I have been able to build very small crates using a toolchain built against this target (together with a later version of `object`) using the configuration described in the target platform-support documentation, although getting anything of substantial complexity to build quickly hits errors in the llvm backend
2025-01-05Remove other maintainersknickish-2/+0
Co-authored-by: Jubilee <workingjubilee@gmail.com>
2025-01-05Auto merge of #135074 - wzssyqa:mips-mti, r=oli-obkbors-0/+34
Target: Add mips mti baremetal support Do the same thing as gcc, which use the vendor `mti` to mark the toolchain as MIPS32r2 default. We support both big endian and little endian flavor: mips-mti-none-elf mipsel-mti-none-elf
2025-01-05Update src/doc/rustc/src/platform-support/mips-mti-none-elf.mdYunQiang Su-1/+1
Co-authored-by: Oli Scherer <github35764891676564198441@oli-obk.de>
2025-01-04Rollup merge of #134996 - bdbai:uwp-support, r=jieyouxu,ChrisDentonJubilee-5/+58
Add UWP (msvc) target support page - Added Platform Support page for `x86_64-uwp-windows-msvc`, `i686-uwp-windows-msvc`, `thumbv7a-uwp-windows-msvc` and `aarch64-uwp-windows-msvc` - Adding myself as a maintainer - Removing the ticks for `thumbv7a-pc-windows-msvc` and `thumbv7a-uwp-windows-msvc` as they do not currently build due to #134565 and https://github.com/rust-lang/backtrace-rs/pull/685 - Fixed a few minor issues to let most of the UWP targets compile - Happy new year to all! r? jieyouxu
2025-01-04Apply suggestions from workingjubilee's code reviewknickish-11/+11
Co-authored-by: Jubilee <workingjubilee@gmail.com>
2025-01-03add m68k-unknown-none-elf targetkirk-0/+112
2025-01-03Target: Add mips mti baremetal supportYunQiang Su-0/+34
Do the same thing as gcc, which use the vendor `mti` to mark the toolchain as MIPS32r2 default. We support both big endian and little endian flavor: mips-mti-none-elf mipsel-mti-none-elf
2025-01-03Add UWP support pagebdbai-5/+58
2025-01-02Make the `test` cfg a "userspace" check-cfgUrgau-2/+4
2024-12-31Rollup merge of #134610 - tbu-:pr_doc_target_fmt, r=NoratriebMatthias Krüger-8/+8
Format `build.toml` consistently in platform support docs Also fix compiler team name in target tier docs.
2024-12-30Rollup merge of #132477 - Noratrieb:illumos-oxide, r=workingjubileeMatthias Krüger-2/+45
Add illumos target documentation Fixes https://github.com/rust-lang/rust/pull/130132#issuecomment-2339055221 `@jclulow` `@pfmooney` I'm adding you as requested. The page is very barebones (as I do not know illumos well) and could use some improvements (for example in the "Cross-compilation toolchains and C code" section). Feel free to suggest improvements (or rewrite it from scratch) if you find something.
2024-12-30Add illumos target documentationNoratrieb-2/+45
2024-12-29Auto merge of #134901 - matthiaskrgr:rollup-b0wwuht, r=matthiaskrgrbors-1/+1
Rollup of 4 pull requests Successful merges: - #134870 (Fix sentence fragment in `pin` module docs) - #134884 (Fix typos) - #134892 (Added codegen test for elidings bounds check when indexes are manually checked) - #134894 (Document how to run the split Docker pipelines) r? `@ghost` `@rustbot` modify labels: rollup
2024-12-29Rollup merge of #134884 - calciumbe:patch1, r=jieyouxuMatthias Krüger-1/+1
Fix typos Hello, I fix some typos in docs and comments. Thank you very much.
2024-12-29Auto merge of #134765 - Noratrieb:linux-none-cant-unwind-silly, r=jieyouxubors-0/+5
Improve default target options for x86_64-unknown-linux-none Without a standard library, we cannot unwind, so it should be panic=abort by default. Additionally, it does not have std because while it is Linux, it cannot use libc, which std uses today for Linux. Using PIE by default may be surprising to users, as shown in #134763, so I've documented it explicitly. I'm not sure if we want to count that as fixing the issue or not. cc `@morr0ne,` as you added the target (and are the maintainer), and `@Noratrieb,` who reviewed that PR (:D).
2024-12-29Document x86_64-unknown-linux-none is PIE by defaultNoratrieb-0/+5
2024-12-29docs: fix typosdxsullivan-3/+3
2024-12-29fix: typoscalciumbe-1/+1
Signed-off-by: calciumbe <192480234+calciumbe@users.noreply.github.com>
2024-12-27Sort triples by name in platform_support.md9names-52/+52
2024-12-22Add platform docs for FreeBSD.Alan Somers-8/+65
2024-12-21Fix compiler team name in target tier docsTobias Bucher-1/+1
2024-12-21Format `build.toml` consistently in platform support docsTobias Bucher-7/+7
2024-12-21on pair → on parTobias Bucher-2/+2
2024-12-17Rollup merge of #133801 - Gelbpunkt:powerpc64le-unknown-linux-musl-tier-2, ↵Matthias Krüger-1/+50
r=jieyouxu,Urgau,Kobzol Promote powerpc64le-unknown-linux-musl to tier 2 with host tools MCP: https://github.com/rust-lang/compiler-team/issues/803 I'm using crosstool-ng for building a toolchain because GCC 9 from `musl-toolchain.sh` has float ABI issues (?) and can't compile LLVM, and writing a crosstool-ng config for a target feels less hacky than yet another target specific shell script. I also defined a kernel version, since there wasn't one specified before. If a lower version is desired, just let me know. I also tried to match the rust configure args with the loongarch64 musl tier 2 target. The resulting compiler works fine, built with `DEPLOY=1 ./src/ci/docker/run.sh dist-powerpc64le-linux` and tested on Alpine Linux in a VM and on a bare metal POWER8 machine: ``` qemu-ppc64le:/tmp/rust-nightly-powerpc64le-unknown-linux-musl$ ash install.sh install: creating uninstall script at /usr/local/lib/rustlib/uninstall.sh install: installing component 'rustc' install: installing component 'rust-std-powerpc64le-unknown-linux-musl' install: installing component 'cargo' install: installing component 'rustfmt-preview' install: installing component 'rls-preview' install: installing component 'rust-analyzer-preview' install: installing component 'llvm-tools-preview' install: installing component 'clippy-preview' install: installing component 'miri-preview' install: installing component 'rust-analysis-powerpc64le-unknown-linux-musl' install: installing component 'llvm-bitcode-linker-preview' install: WARNING: failed to run ldconfig. this may happen when not installing as root. run with --verbose to see the error rust installed. qemu-ppc64le:~$ echo 'fn main() { println!("hello world"); }' > test.rs qemu-ppc64le:~$ rustc test.rs qemu-ppc64le:~$ ./test hello world qemu-ppc64le:~$ file test test: ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, OpenPOWER ELF V2 ABI, version 1 (SYSV), statically linked, BuildID[sha1]=596ee6abf9add487ebc54fb71c2076fb6faea013, with debug_info, not stripped ``` try-job: dist-powerpc64le-linux
2024-12-14Rollup merge of #133293 - psumbera:solaris-maintainer, ↵Matthias Krüger-2/+36
r=workingjubilee,jieyouxu,tgross35 Updates Solaris target information, adds Solaris maintainer
2024-12-13Fix powerpc64 big-endian FreeBSD ABITaiki Endo-1/+1
2024-12-06Update src/doc/rustc/src/platform-support/powerpc64le-unknown-linux-musl.mdJens Reidel-1/+1
Co-authored-by: famfo <famfo@famfo.xyz>
2024-12-06Fix markdown linkJens Reidel-1/+1
Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2024-12-06Promote powerpc64le-unknown-linux-musl to tier 2 with host toolsJens Reidel-1/+50
MCP: https://github.com/rust-lang/compiler-team/issues/803 Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2024-12-05Fix "std" support status of some tier 3 targetsTaiki Endo-8/+8
2024-11-29Rollup merge of #133577 - uweigand:s390x-doc-cloudaccess, r=jieyouxuMatthias Krüger-0/+16
Document s390x machine access via community cloud
2024-11-28Document s390x machine access via community cloudUlrich Weigand-0/+16
2024-11-28chore: fix 404 status URLlongxiangqiao-1/+1
Signed-off-by: longxiangqiao <longxiangqiao@qq.com>
2024-11-25Rollup merge of #133297 - DianQK:embed-bitcode-ios, r=nikic许杰友 Jieyou Xu (Joe)-8/+5
Remove legacy bitcode for iOS Follow #117364.
2024-11-24embed-bitcode is no longer used in iOSDianQK-8/+5
2024-11-22Stabilize the 2024 editionEric Huss-1/+1
2024-11-22Updates Solaris target information, adds Solaris maintainerPetr Sumbera-2/+36
2024-11-19Correct the tier listing of `wasm32-wasip2`Alex Crichton-1/+1
This target is tier 2, not tier 3, and I forgot to update this. Closes #133206
2024-11-18Update src/doc/rustc/src/platform-support/s390x-unknown-linux-gnu.mdUlrich Weigand-0/+1
Co-authored-by: Josh Stone <cuviper@gmail.com>
2024-11-18Document s390x-unknown-linux targetsUlrich Weigand-2/+199
This adds documentation for the following existing targets: s390x-unknown-linux-gnu (Tier 2 with host tools) s390x-unknown-linux-musl (Tier 3) I volunteer as maintainer for these targets going forward. Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>
2024-11-03Remove the `wasm32-wasi` target from rustcAlex Crichton-7/+2
This commit is the final step in the journey of renaming the historical `wasm32-wasi` target in the Rust compiler to `wasm32-wasip1`. Various steps in this journey so far have been: * 2023-04-03: rust-lang/compiler-team#607 - initial proposal for this rename * 2024-11-27: rust-lang/compiler-team#695 - amended schedule/procedure for rename * 2024-01-29: rust-lang/rust#120468 - initial introduction of `wasm32-wasip1` * 2024-06-18: rust-lang/rust#126662 - warn on usage of `wasm32-wasi` * 2024-11-08: this PR - remove the `wasm32-wasi` target The full transition schedule is in [this comment][comment] and is summarized with: * 2024-05-02: Rust 1.78 released with `wasm32-wasip1` target * 2024-09-05: Rust 1.81 released warning on usage of `wasm32-wasi` * 2025-01-09: Rust 1.84 to be released without the `wasm32-wasi` target This means that support on stable for the replacement target of `wasm32-wasip1` has currently been available for 6 months. Users have already seen warnings on stable for 2 months about usage of `wasm32-wasi` and stable users have another 2 months of warnings before the target is removed from stable. This commit is intended to be the final step in this transition so the source tree should no longer mention `wasm32-wasi` except in historical reference to the older name of the `wasm32-wasip1` target. [comment]: https://github.com/rust-lang/rust/pull/120468#issuecomment-1977878747
2024-11-02Add `--print host-triple`Noratrieb-2/+3
People often parse `-vV` output to get to the host triple, which is annoying to do. It's easier to just get it directly.
2024-11-02Rollup merge of #131829 - Zalathar:goodbye-zprofile, r=chenyukangGuillaume Gomez-6/+2
Remove support for `-Zprofile` (gcov-style coverage instrumentation) Tracking issue: #42524 MCP: https://github.com/rust-lang/compiler-team/issues/798 --- This PR removes the unstable `-Zprofile` flag, which enables ”gcov-style” coverage instrumentation, along with its associated `-Zprofile-emit` configuration flag. (The profile flag predates and is almost entirely separate from the stable `-Cinstrument-coverage` flag.) Notably, the `-Zprofile` flag: - Is largely untested in-tree, having only one run-make test that does not check whether its output is correct or useful. - Has no known maintainer. - Has seen no push towards stabilization. - Has at least one severe regression reported in 2022 that apparently remains unaddressed. - #100125 - Is confusingly named, since it appears to be more about coverage than performance profiling, and has nothing to do with PGO. - Is fundamentally limited by relying on counters auto-inserted by LLVM, with no knowledge of Rust beyond debuginfo.
2024-10-31Document the difference between Clang's `-darwin` and `-macosx` targetsMads Marquart-0/+5
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-10 07:21:34 +0000