about summary refs log tree commit diff
path: root/src/doc
AgeCommit message (Collapse)AuthorLines
2023-01-13Change `src/test` to `tests` (#1547)Albert Larsan-110/+110
2023-01-11Stabilize `abi_efiapi` featureNicholas Bishop-23/+0
Tracking issue: https://github.com/rust-lang/rust/issues/65815
2023-01-11add full name for ICE (#1552)gftea-2/+2
Co-authored-by: Yuki Okushi <huyuumi.dev+love@gmail.com>
2023-01-11Change `src/test` to `tests` in source files, fix tidy and testsAlbert Larsan-4/+4
2023-01-10Fix incorrect links (#1549)Mu00-2/+2
2023-01-10fix rebase linkoskgo-1/+1
2023-01-09Accept old spelling of Fuchsia target triplesDavid Koloski-0/+2
Because the old spelling is widely used, some projects may need time to migrate their uses to the new triple spelling. The old spelling may eventually be removed altogether.
2023-01-08rustdoc: fix outdated lint section of the bookMichael Howell-1/+1
2023-01-05Add vendor to Fuchsia's target tripleDavid Koloski-52/+52
Historically, Rust's Fuchsia targets have been labeled x86_64-fuchsia and aarch64-fuchsia. However, they should technically contain vendor information. This CL changes Fuchsia's target triples to include the "unknown" vendor since Clang now does normalization and handles all triple spellings. This was previously attempted in #90510, which was closed due to inactivity.
2023-01-04Rollup merge of #106464 - djkoloski:update_fuchsia_platform_support_docs, ↵Michael Goulet-0/+3
r=tmandry Update Fuchsia walkthrough with new configs The new `download-ci-llvm` configuration option dosn't work with `lld = true` (see #100853). The Fuchsia walkthrough should recommend setting it to `false`. r? `@tmandry`
2023-01-04Update Fuchsia walkthrough with new configsDavid Koloski-0/+3
The new `download-ci-llvm` configuration option dosn't work with `lld = true` (see #100853). The Fuchsia walkthrough should recommend setting it to `false`.
2023-01-04Rollup merge of #106274 - jyn514:dump-mono-stats, r=lqdMatthias Krüger-0/+20
Add JSON output to -Zdump-mono-stats Follow-up to https://github.com/rust-lang/rust/pull/105481 r? `@lqd` cc `@wesleywiser`
2023-01-03Auto merge of #105712 - amg98:feat/vita-support, r=wesleywiserbors-0/+129
PlayStation Vita support Just the compiler definitions for no-std projects and std support using newlib Earlier PR: https://github.com/rust-lang/rust/pull/105606
2023-01-02Add a section for how to review code more easily (#1538)Joshua Nelson-0/+38
- How to hide whitespace - Fetching PRs without having to add a new remote or copy-paste the URL of the author's fork - How to review large blocks that have moved - Suggest `git range-diff`. This section is still mostly incomplete; fixing an exact command that will work seems kinda tricky and I don't currently have time for it.
2023-01-02Add json output to `-Zdump-mono-stats`Joshua Nelson-0/+20
This allows analyzing the output programatically; for example, finding the item with the highest `total_estimate`. I also took the liberty of adding `untracked` tests to `rustc_session` and documentation to the unstable book for `dump-mono-items`.
2023-01-02Update booksrustbot-0/+0
2022-12-31fix typoJoshua Nelson-1/+1
Co-authored-by: Noah Lev <camelidcamel@gmail.com>
2022-12-31Give help for when you update a submodule by accidentJoshua Nelson-0/+27
2022-12-31Update sentence about LLVM to match the new defaultsJoshua Nelson-2/+2
2022-12-31Move information about dependencies to the rust-lang/rust readmeJoshua Nelson-50/+3
This avoids having to maintain the information in two places.
2022-12-31Move "create a config.toml" after the section explaning x.pyJoshua Nelson-12/+12
2022-12-31Remove unnecessary detail in building chapterJoshua Nelson-71/+16
Most of these details were not helpful or necessary for building the compiler for the first time. This section comes very early in the guide and is meant to be a tutorial, so being concise is very important.
2022-12-31Remove initial section on submodulesJoshua Nelson-12/+0
It's not necessary and it takes up valuable space at the very start of the guide.
2022-12-31Replace `$TARGET` with `host`Joshua Nelson-13/+8
This avoids having to manually modify the configuration in the docs.
2022-12-30Added link from Targets to Platform Support in the bookTrevor Gross-1/+4
2022-12-29Use `origin` consistently and add an example of rebasing over the wrong remoteJoshua Nelson-10/+27
2022-12-29Add more rebasing helpJoshua Nelson-2/+41
2022-12-27Fix doc comment parsingkraktus-2/+2
This can actually make a difference for the user if they rely on unicode formating. Prompted by https://github.com/dtolnay/syn/issues/771
2022-12-25Fix rustc_borrowck crate name typo (#1535)Dan Mezhiborsky-1/+1
2022-12-19Update booksrustbot-0/+0
2022-12-18Apply feedbackmejrs-4/+4
2022-12-18Add -Ztrack-diagnostics informationmejrs-1/+37
2022-12-17Auto merge of #105421 - jacobbramley:jb/branch-prot-check, r=nagisabors-1/+1
Check AArch64 branch-protection earlier in the pipeline. As suggested in #93516. r? `@nagisa`
2022-12-16remove relative links from `rustc-book` and `unstable-book`Ezra Shaw-23/+23
Co-authored-by: Joshua Nelson <github@jyn.dev>
2022-12-14Added PlayStation Vita supportAndrés Martínez-0/+129
2022-12-14Add documentation for LLVM KCFI support (#1529)Ramon de C Valle-3/+8
This commit adds initial documentation for LLVM Kernel Control Flow Integrity (KCFI) support to the Rust compiler (see rust-lang/rust#105109 and rust-lang/rust#89653).
2022-12-14typoTshepang Mbambo-1/+1
2022-12-14Replace NoLandingPad with another alive VisitorMohammad Omidvar-5/+3
The broken reference to the non-existing `NoLandingPad` is replaced by `LocalUseCounter` to fix this document.
2022-12-14Remove todo noteMohammad Omidvar-1/+0
2022-12-14Replace NoLandingPad with another alive MIR passMohammad Omidvar-4/+3
The broken reference to `NoLandingPad` is replaced by `RemoveStorageMarkers` to fix this document.
2022-12-10doc: document remap matching behaviour in rustc flagsAlexis (Poliorcetics) Bourget-0/+3
2022-12-10Rollup merge of #105109 - rcvalle:rust-kcfi, r=bjorn3Matthias Krüger-0/+30
Add LLVM KCFI support to the Rust compiler This PR adds LLVM Kernel Control Flow Integrity (KCFI) support to the Rust compiler. It initially provides forward-edge control flow protection for operating systems kernels for Rust-compiled code only by aggregating function pointers in groups identified by their return and parameter types. (See llvm/llvm-project@cff5bef.) Forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space) will be provided in later work as part of this project by identifying C char and integer type uses at the time types are encoded (see Type metadata in the design document in the tracking issue #89653). LLVM KCFI can be enabled with -Zsanitizer=kcfi. Thank you again, `@bjorn3,` `@eddyb,` `@nagisa,` and `@ojeda,` for all the help!
2022-12-08share same linkTshepang Mbambo-2/+2
2022-12-08chore: Update `actions/github-script` to v6Yuki Okushi-3/+2
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
2022-12-08Add documentation for LLVM KCFI supportRamon de C Valle-0/+30
This commit adds initial documentation for LLVM Kernel Control Flow Integrity (KCFI) support to the Rust compiler (see #105109 and #89653). Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
2022-12-09fix: Fix broken linksYuki Okushi-8/+9
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
2022-12-08Remove TySOli Scherer-16/+14
2022-12-06Fix small inaccuracy in monomorph pageJared Harp-1/+1
2022-12-06unstable-book: Add `ignore` to `abi_efiapi` example codeNicholas Bishop-1/+1
This example doesn't compile on targets that don't support UEFI, as reported here: https://github.com/rust-lang/rust/pull/104793#issuecomment-1339783727
2022-12-06Correct branch-protection documentation.Jacob Bramley-1/+1
The branch-protection codegen option has always been treated as an error for non-AArch64 targets.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 06:11:16 +0000