about summary refs log tree commit diff
path: root/src/doc/rustc
AgeCommit message (Collapse)AuthorLines
2022-08-31Fix a bunch of typoDezhi Wu-4/+4
This PR will fix some typos detected by [typos]. I only picked the ones I was sure were spelling errors to fix, mostly in the comments. [typos]: https://github.com/crate-ci/typos
2022-08-31Rollup merge of #101025 - semarie:openbsd-archs, r=petrochenkovMatthias Krüger-0/+4
Add tier-3 support for powerpc64 and riscv64 openbsd # powerpc64 - MCP for [powerpc64-unknown-openbsd tier-3 support](https://github.com/rust-lang/compiler-team/issues/551) - only need to add spec definition in rustc_target # riscv64 - MCP for [riscv64-unknown-openbsd tier-3 support](https://github.com/rust-lang/compiler-team/issues/552) - add spec definition in rustc_target - follow freebsd about avoiding linking with `libatomic`
2022-08-31Rollup merge of #100927 - andrewpollack:fuchsia-docs-rustup, r=tmandryYuki Okushi-97/+426
Adding new Fuchsia rustup docs... reworking walkthrough Docs improvements: * Adding new `rustup` target add for Fuchsia targets * Reworking walkthrough to show directory building as it happens * Reworking walkthrough to use `hello_fuchsia_pkg/` directory cc. `@djkoloski`
2022-08-30Update src/doc/rustc/src/platform-support/fuchsia.mdandrewpollack-1/+1
Co-authored-by: Tyler Mandry <tmandry@gmail.com>
2022-08-30Update src/doc/rustc/src/platform-support/fuchsia.mdandrewpollack-1/+1
Co-authored-by: Tyler Mandry <tmandry@gmail.com>
2022-08-30Adding new Fuchsia rustup docs... reworking walkthroughAndrew Pollack-96/+425
2022-08-28add riscv64gc-unknown-openbsd support (target riscv64-unknown-openbsd on ↵Sébastien Marie-0/+2
OpenBSD) - add platform-support documentation - add riscv64gc-unknown-openbsd spec - do not try to link with -latomic on openbsd
2022-08-28add powerpc64-unknown-openbsd supportSébastien Marie-0/+2
2022-08-23Rollup merge of #100641 - corwinkuiper:add-armv4t-target, r=oli-obkMatthias Krüger-0/+1
Add the armv4t-none-eabi target to the supported_targets This target was added in #100244 but forgot to add it to the macro in the `mod.rs` file. ``@Lokathor``
2022-08-18Rollup merge of #100637 - andrewpollack:fuchsia-docs-adjustments, r=tmandryMatthias Krüger-3/+17
Improving Fuchsia rustc support documentation * Adjusting `package/meta/package` to fit current schema * Adding repository server step * Adjusting step to give default repository * Adding "recreate" step for easier step following
2022-08-16add target armv4t-none-eabiCorwin-0/+1
2022-08-16Improving Fuchsia rustc support documentationAndrew Pollack-3/+17
Improving wording
2022-08-16Rollup merge of #100384 - ridwanabdillahi:instr_profile_output, r=wesleywiserMatthias Krüger-8/+20
Add support for generating unique profraw files by default when using `-C instrument-coverage` Currently, enabling the rustc flag `-C instrument-coverage` instruments the given crate and by default uses the naming scheme `default.profraw` for any instrumented profile files generated during the execution of a binary linked against this crate. This leads to multiple binaries being executed overwriting one another and causing only the last executable run to contain actual coverage results. This can be overridden by manually setting the environment variable `LLVM_PROFILE_FILE` to use a unique naming scheme. This PR adds a change to add support for a reasonable default for rustc to use when enabling coverage instrumentation similar to how the Rust compiler treats generating these same `profraw` files when PGO is enabled. The new naming scheme is set to `default_%m_%p.profraw` to ensure the uniqueness of each file being generated using [LLVMs special pattern strings](https://clang.llvm.org/docs/SourceBasedCodeCoverage.html#running-the-instrumented-program). Today the compiler sets the default for PGO `profraw` files to `default_%m.profraw` to ensure a unique file for each run. The same can be done for the instrumented profile files generated via the `-C instrument-coverage` flag as well which LLVM has API support for. Linked Issue: https://github.com/rust-lang/rust/issues/100381 r? `@wesleywiser`
2022-08-13Auto merge of #100341 - andrewpollack:fuchsia-llvm-libunwind, r=tmandrybors-6/+0
Use llvm-libunwind="in-tree" for Fuchsia targets With updates to Fuchsia CI's Zircon libraries #99833, we can introduce `llvm-libunwind="in-tree"` for Fuchsia targets. This PR restores functionality removed from https://github.com/rust-lang/rust/pull/93604#issuecomment-1136515651. cc `@tmandry` `@djkoloski`
2022-08-12Respond to PR comments. Cleanup documentation.ridwanabdillahi-13/+17
2022-08-12Respond to RFC comments.ridwanabdillahi-16/+24
2022-08-10Rollup merge of #100072 - oToToT:patch-1, r=michaelwoeristerMatthias Krüger-2/+2
linker-plugin-lto.md: Correct the name of example c file The final output is linked with `cmain.o`, but we use `main.o` in the example. This patch changes the name to `cmain.c` and `cmain.o` as the "C/C++ code as a dependency in Rust" section.
2022-08-09LLVM lib unwind fuchsia configAndrew Pollack-6/+0
Removing libunwind from Fuchsia target docs
2022-08-07Update SUMMARY.mdLokathor-0/+1
2022-08-07Create armv4t_none_eabi.mdLokathor-0/+70
2022-08-03doc: s390x also requires glibc 2.17Josh Stone-1/+1
Co-authored-by: Jubilee <46493976+workingjubilee@users.noreply.github.com>
2022-08-03Increase the minimum linux-gnu versionsJosh Stone-7/+7
This is implementing the MCP from rust-lang/compiler-team#493. It is increasing the minimum requirements of a couple Tier 1 targets, and others at lower tiers, so this should go through FCP sign-offs for both `T-compiler` and `T-release`. The new `linux-gnu` baseline is kernel 3.2 and glibc 2.17. We will also take that kernel as the minimum floor for _all_ `*-linux-*` targets, so it may be broadly assumed in the implementation of the standard library. That does not preclude specific targets from having greater requirements where it makes sense, like a new arch needing something newer, or a platform like `linux-android` choosing a newer baseline.
2022-08-02rustc-docs: Be less specific about the representation of `+bundle`Vadim Petrochenkov-3/+3
2022-08-03linker-plugin-lto.md: Correct the name of example c fileTommy Chiang-2/+2
2022-07-30Rollup merge of #99831 - djkoloski:add_fuchsia_target_documentation, r=tmandryYuki Okushi-0/+296
Add Fuchsia platform support documentation This documentation contains instructions for building and running binaries on Fuchsia using its provided SDK.
2022-07-29Rollup merge of #99845 - xtexChooser:patch-1, r=GuillaumeGomezYuki Okushi-2/+2
Remove `$` prefix for bash scripts in doc
2022-07-28Add Fuchsia platform support documentationDavid Koloski-0/+296
2022-07-28Update custom.mdxtexChooser-2/+2
2022-07-27doc/rustc: describe the uefi target platformsDavid Rheinsberg-0/+255
Add a `platform-support` entry to the rustc-docs for the different `*-unknown-uefi` targets. This describes in detail how this platform works, a few basic examples, and how to compile for the platform. Red Hat is sponsoring my work on this platform, so I am putting myself down as target maintainer. Co-maintainers are more than welcome to join me in the effort. Communication is going on off-list to coordinate the different efforts. Note that the ultimate goal is to move the UEFI targets to Tier-2 so bootloaders can be more easily supported in commercial products. This documentation is the first step towards that goal, but should be a viable documentation even for the current Tier-3 status of the targets. I also want to point out that there is an ongoing GSoC-effort to port the rust standard library to UEFI (by Ayush Singh). While this work is not necessarily required to get to Tier-2, we definitely should coordinate the efforts and update the documentation as soon as any such ports are merged. Note that the targets are already used by multiple commercial and non commercial production systems, including, but not limited to: * Tianocore-EDK2 (Official UEFI SDK by Intel) comes with rust support in its staging repository (not part of any release, yet). (https://github.com/tianocore/edk2-staging/tree) * Intel's research program "Project Mu" uses the rust UEFI targets to show possible future replacements for Tianocore-EDK2. * The Rust OS "Redox" uses the UEFI targets for its bootloader. (https://www.redox-os.org/) * The hugely popular in-depth documentation of OS development in Rust by Philipp Oppermann uses the UEFI targets. (https://os.phil-opp.com/) Signed-off-by: David Rheinsberg <david.rheinsberg@gmail.com>
2022-07-14Rename aarch64-nintendo-switch to aarch64-nintendo-switch-freestandingleo60228-6/+6
2022-07-14Add aarch64-nintendo-switch.md to SUMMARY.mdleo60228-0/+1
I can't think of any other reason CI might be failing, and I should've done this anyway.
2022-07-14Add docs for Switch targetleo60228-1/+50
2022-07-14Add Nintendo Switch tier 3 targetjam1garner-0/+1
2022-06-13Add platform-support page for armv6k-nintendo-3dsIan Chamberlain-1/+132
Co-authored-by: Mark Drobnak <mark.drobnak@gmail.com>
2022-06-13Add Apple WatchOS compile targetsVladimir Michael Eatwell-0/+60
2022-06-09Stabilize the `bundle` native library modifierVadim Petrochenkov-0/+20
2022-06-04platform-support: add riscv32imac-unknown-xous-elfSean Cross-0/+52
Signed-off-by: Sean Cross <sean@xobs.io>
2022-05-20Rollup merge of #97203 - ehuss:rustc-summary-formatting, r=Dylan-DPCMatthias Krüger-20/+20
Minor tweaks to rustc book summary formatting. This includes a few minor tweaks to the summary/titles of chapters for the rustc book: * Use a consistent chapter capitalization and hyphenation. * Move "Codegen Options" underneath "Command-line Arguments". I feel like they are two closely related chapters, where codegen is just a subset of the total arguments. * Move "Target Tier Policy" underneath "Platform Support". That chapter includes that policy for platform support, and thus I feel it is more closely related to that grouping.
2022-05-19Minor tweaks to rustc book summary formatting.Eric Huss-20/+20
2022-05-20Fix typoydah-2/+2
This PR is fixes typo "avaiable" to "available".
2022-05-15rustc: Stricter checking for #[link] attributesVadim Petrochenkov-1/+2
2022-05-13Add LLVM based mingw-w64 targetsMateusz Mikuła-0/+51
2022-05-12Fix platform support links.Eric Huss-1/+1
2022-05-12Rollup merge of #95896 - nagisa:nvptx-contacts, r=Mark-SimulacrumMatthias Krüger-0/+58
Note the contacts for the nvptx64 target(s) cc `@RDambrosio016` `@kjetilkjeka`
2022-05-10Rollup merge of #93661 - ehuss:add-missing-rustc-arg-docs, ↵Dylan DPC-0/+44
r=estebank,Mark-Simulacrum Add missing rustc arg docs Add documentation for recently added rustc args `-C symbol-mangling-version` was stabilized in #90128. `--json=future-incompat` was stabilized in #91535.
2022-05-02Fix typo in lint levels docRock Boynton-3/+2
2022-04-26linker: Stop using whole-archive on dependencies of dylibsVadim Petrochenkov-2/+2
https://github.com/rust-lang/rust/pull/95604 implemented a better and more fine-grained way of keeping exported symbols alive.
2022-04-16Rollup merge of #94605 - Michcioperz:patch-1, r=pnkfelixDylan DPC-3/+6
Add missing links in platform support docs I was looking at m68k support and saw that https://doc.rust-lang.org/rustc/platform-support.html and the sidebar there were missing some links to target documentation
2022-04-14docs: Update tests chapter for Termination stabilizationEric Huss-1/+3
2022-04-12fix broken link in coverage tools docsAnthonyMikh-1/+1
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 05:17:22 +0000