| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Add v0 symbol mangling for `f16` and `f128`
As discussed at <https://github.com/rust-lang/rust/pull/122106>, use the crate encoding to represent new primitives.
|
|
As discussed at <https://github.com/rust-lang/rust/pull/122106>, use the
crate encoding to represent new primitives.
|
|
Add x86_64-unknown-linux-none target
Adds a freestanding linux binary with no libc dependency. This is useful for writing programs written only in rust. It is also essential for writing low level stuff like libc or a dynamic linker.
Tier 3 policy:
>A tier 3 target must have a designated developer or developers (the "target maintainers") on record to be CCed when issues arise regarding the target. (The mechanism to track and CC such developers may evolve over time.)
I will be the designed maintainer for this target
>Targets must use naming consistent with any existing targets; for instance, a target for the same CPU or OS as an existing Rust target should use the same name for that CPU or OS. Targets should normally use the same names and naming conventions as used elsewhere in the broader ecosystem beyond Rust (such as in other toolchains), unless they have a very good reason to diverge. Changing the name of a target can be highly disruptive, especially once the target reaches a higher tier, so getting the name right is important even for a tier 3 target.
The target triple is consistent with other targets
>Target names should not introduce undue confusion or ambiguity unless absolutely necessary to maintain ecosystem compatibility. For example, if the name of the target makes people extremely likely to form incorrect beliefs about what it targets, the name should be changed or augmented to disambiguate it.
If possible, use only letters, numbers, dashes and underscores for the name. Periods (.) are known to cause issues in Cargo.
There is no confusion with other targets since it explicitly adds "none" at the end instead of omitting the environment
>Tier 3 targets may have unusual requirements to build or use, but must not create legal issues or impose onerous legal terms for the Rust project or for Rust developers or users.
The target does not introduce any unusual requirement
>The target must not introduce license incompatibilities.
There are no license incompatibilities
> Anything added to the Rust repository must be under the standard Rust license (MIT OR Apache-2.0).
Everything added is under that license
>The target must not cause the Rust tools or libraries built for any other host (even when supporting cross-compilation to the target) to depend on any new dependency less permissive than the Rust licensing policy. This applies whether the dependency is a Rust crate that would require adding new license exceptions (as specified by the tidy tool in the rust-lang/rust repository), or whether the dependency is a native library or binary. In other words, the introduction of the target must not cause a user installing or running a version of Rust or the Rust tools to be subject to any new license requirements.
There are no new dependencies
>Compiling, linking, and emitting functional binaries, libraries, or other code for the target (whether hosted on the target itself or cross-compiling from another target) must not depend on proprietary (non-FOSS) libraries. Host tools built for the target itself may depend on the ordinary runtime libraries supplied by the platform and commonly used by other applications built for the target, but those libraries must not be required for code generation for the target; cross-compilation to the target must not require such libraries at all. For instance, rustc built for the target may depend on a common proprietary C runtime library or console output library, but must not depend on a proprietary code generation library or code optimization library. Rust's license permits such combinations, but the Rust project has no interest in maintaining such combinations within the scope of Rust itself, even at tier 3.
There is no proprietary dependencies
>"onerous" here is an intentionally subjective term. At a minimum, "onerous" legal/licensing terms include but are not limited to: non-disclosure requirements, non-compete requirements, contributor license agreements (CLAs) or equivalent, "non-commercial"/"research-only"/etc terms, requirements conditional on the employer or employment of any particular Rust developers, revocable terms, any requirements that create liability for the Rust project or its developers or users, or any requirements that adversely affect the livelihood or prospects of the Rust project or its developers or users.
No such terms exist for this target
>Neither this policy nor any decisions made regarding targets shall create any binding agreement or estoppel by any party. If any member of an approving Rust team serves as one of the maintainers of a target, or has any legal or employment requirement (explicit or implicit) that might affect their decisions regarding a target, they must recuse themselves from any approval decisions regarding the target's tier status, though they may otherwise participate in discussions.
>This requirement does not prevent part or all of this policy from being cited in an explicit contract or work agreement (e.g. to implement or maintain support for a target). This requirement exists to ensure that a developer or team responsible for reviewing and approving a target does not face any legal threats or obligations that would prevent them from freely exercising their judgment in such approval, even if such judgment involves subjective matters or goes beyond the letter of these requirements.
Understood
>Tier 3 targets should attempt to implement as much of the standard libraries as possible and appropriate (core for most targets, alloc for targets that can support dynamic memory allocation, std for targets with an operating system or equivalent layer of system-provided functionality), but may leave some code unimplemented (either unavailable or stubbed out as appropriate), whether because the target makes it impossible to implement or challenging to implement. The authors of pull requests are not obligated to avoid calling any portions of the standard library on the basis of a tier 3 target not implementing those portions.
The target already implements core. It might be possible in the future to add support for alloc and std by leveraging crates such as [origin](https://github.com/sunfishcode/origin/) and [rustix](https://github.com/bytecodealliance/rustix)
> The target must provide documentation for the Rust community explaining how to build for the target, using cross-compilation if possible. If the target supports running binaries, or running tests (even if they do not pass), the documentation must explain how to run such binaries or tests for the target, using emulation if possible or dedicated hardware if necessary.
I believe the proper docs are added
>Tier 3 targets must not impose burden on the authors of pull requests, or other developers in the community, to maintain the target. In particular, do not post comments (automated or manual) on a PR that derail or suggest a block on the PR based on a tier 3 target. Do not send automated messages or notifications (via any medium, including via `@)` to a PR author or others involved with a PR regarding a tier 3 target, unless they have opted into such messages.
> Backlinks such as those generated by the issue/PR tracker when linking to an issue or PR are not considered a violation of this policy, within reason. However, such messages (even on a separate repository) must not generate notifications to anyone involved with a PR who has not requested such notifications.
Understood
> Patches adding or updating tier 3 targets must not break any existing tier 2 or tier 1 target, and must not knowingly break another tier 3 target without approval of either the compiler team or the maintainers of the other tier 3 target.
> In particular, this may come up when working on closely related targets, such as variations of the same architecture with different features. Avoid introducing unconditional uses of features that another variation of the target may not have; use conditional compilation or runtime detection, as appropriate, to let each target run code supported by that target.
No other targets are effected
>Tier 3 targets must be able to produce assembly using at least one of rustc's supported backends from any host target.
The same backends used by other linux targets work without issues
|
|
Co-authored-by: Trevor Gross <t.gross35@gmail.com>
|
|
Migrate `run-make/c-link-to-rust-va-list-fn` to `rmake`
Part of #121876.
r? `@jieyouxu`
|
|
Migrate fuchsia docs from `pm` to `ffx`
The `pm` tool has been deprecated, so this migrates the fuchsia documentation to the new `ffx` based tooling.
|
|
Split out `ty::AliasTerm` from `ty::AliasTy`
Splitting out `AliasTerm` (for use in project and normalizes goals) and `AliasTy` (for use in `ty::Alias`)
r? lcnr
|
|
|
|
The `pm` tool has been deprecated, so this migrates the fuchsia
documentation to the new `ffx` based tooling.
|
|
GuillaumeGomez:migrate-rustdoc-target-spec-json-path, r=jieyouxu
Migrate rustdoc target spec json path
Part of https://github.com/rust-lang/rust/issues/121876.
r? `@jieyouxu`
|
|
|
|
Suggested-by: Caleb Cartwright <calebcartwright@users.noreply.github.com>
|
|
|
|
|
|
Show an example that has bounds.
|
|
In particular, lifetime-generic associated types often have a
`where Self: 'a` bound, which we can format on the same line.
|
|
|
|
|
|
|
|
Rewrite 3 very similar `run-make` alloc tests to rmake
Part of #121876
#121918 attempted to port these 3 tests 2 months ago. However, since then, the structure of `run-make-support` has changed a bit and new helper functions were added. Since there has been no activity on the PR, they are good low-hanging fruit to knock down, using the new functions of the current library.
There is also the removal of a useless import on a very similar test.
|
|
Fix MemCategorization and ExprUse visitors for new solver (this time it's better)
Best reviewed by each commit. Supersedes #124859.
r? lcnr
|
|
|
|
|
|
|
|
|
|
Fix hidden title in rustdoc book
raw html is treated as actual html by markdown, so this title needs to use some form of escaping in order to display correctly
|
|
GuillaumeGomez:migrate-rustdoc-scrape-examples-ordering, r=jieyouxu
Migrate rustdoc scrape examples ordering
Part of https://github.com/rust-lang/rust/issues/121876.
This one adds a lot of utility methods/functions. To prevent having too much changes at once, I didn't make the existing rmake tests use these yet but I'll send a follow-up so they all use it.
r? `@jieyouxu`
|
|
|
|
|
|
use key-value format in stage0 file
Currently, we are working on the python removal task on bootstrap. Which means we have to extract some data from the stage0 file using shell scripts. However, parsing values from the stage0.json file is painful because shell scripts don't have a built-in way to parse json files.
This change simplifies the stage0 file format to key-value pairs, which makes it easily readable from any environment.
See the zulip thread for more details: https://rust-lang.zulipchat.com/#narrow/stream/326414-t-infra.2Fbootstrap/topic/Using.20different.20format.20in.20the.20stage0.20file
|
|
r=jieyouxu
Migrate `run-make/rustdoc-shared-flags` to rmake
Part of https://github.com/rust-lang/rust/issues/121876.
r? ```@jieyouxu```
|
|
r=GuillaumeGomez
Always hide private fields in aliased type
This PR adds a new rustdoc pass that unconditionally always strips all private fields in aliased type, since showing them, even with `--document-private-items`, is confusing, unhelpful, and run backwards to the "Aliased type" feature, which is to show the type as it would be seen by the user.
r? ```@GuillaumeGomez```
Fixes #124938
Fixes #123860
|
|
Enable profiler for armv7-unknown-linux-gnueabihf.
Allow code coverage measurement for armv7-unknown-linux-gnueabihf targets. Fixes #79640.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
Weekly `cargo update`
Automation to keep dependencies in `Cargo.lock` current.
The following is the output from `cargo update`:
```txt
Locking 77 packages to latest compatible versions
Updating allocator-api2 v0.2.16 -> v0.2.18
Updating anstream v0.6.13 -> v0.6.14
Updating anstyle v1.0.6 -> v1.0.7
Updating anstyle-lossy v1.1.0 -> v1.1.1
Updating anstyle-parse v0.2.3 -> v0.2.4
Updating anstyle-query v1.0.2 -> v1.0.3
Updating anstyle-svg v0.1.3 -> v0.1.4
Updating anstyle-wincon v3.0.2 -> v3.0.3
Updating anyhow v1.0.81 -> v1.0.83
Updating autocfg v1.2.0 -> v1.3.0
Updating bumpalo v3.15.4 -> v3.16.0
Updating bytecount v0.6.7 -> v0.6.8
Updating clap_complete v4.5.1 -> v4.5.2
Updating color-print v0.3.5 -> v0.3.6
Updating color-print-proc-macro v0.3.5 -> v0.3.6
Updating colorchoice v1.0.0 -> v1.0.1
Updating dissimilar v1.0.7 -> v1.0.9
Updating either v1.10.0 -> v1.11.0
Updating encoding_rs v0.8.33 -> v0.8.34
Updating errno v0.3.8 -> v0.3.9
Updating fastrand v2.0.2 -> v2.1.0
Updating flate2 v1.0.28 -> v1.0.30
Updating fluent-bundle v0.15.2 -> v0.15.3
Updating fluent-syntax v0.11.0 -> v0.11.1
Updating getrandom v0.2.13 -> v0.2.14 (latest: v0.2.15)
Updating hashbrown v0.14.3 -> v0.14.5
Updating intl-memoizer v0.5.1 -> v0.5.2
Adding is_terminal_polyfill v1.70.0
Updating jobserver v0.1.28 -> v0.1.31
Updating lock_api v0.4.11 -> v0.4.12
Updating num-traits v0.2.18 -> v0.2.19
Removing packed_simd v0.3.9
Updating parking_lot v0.12.1 -> v0.12.2
Updating parking_lot_core v0.9.9 -> v0.9.10
Updating pest v2.7.9 -> v2.7.10
Updating pest_derive v2.7.9 -> v2.7.10
Updating pest_generator v2.7.9 -> v2.7.10
Updating pest_meta v2.7.9 -> v2.7.10
Updating proc-macro2 v1.0.79 -> v1.0.82
Updating pulldown-cmark v0.10.2 -> v0.10.3
Updating pulldown-cmark-escape v0.10.0 -> v0.10.1
Updating quote v1.0.35 -> v1.0.36
Adding redox_syscall v0.5.1
Updating rustc-demangle v0.1.23 -> v0.1.24
Updating rustix v0.38.32 -> v0.38.34
Updating rustversion v1.0.15 -> v1.0.16
Updating ryu v1.0.17 -> v1.0.18
Updating security-framework v2.10.0 -> v2.11.0
Updating security-framework-sys v2.10.0 -> v2.11.0
Updating self_cell v1.0.3 -> v1.0.4
Updating semver v1.0.22 -> v1.0.23
Updating serde v1.0.197 -> v1.0.201
Updating serde_derive v1.0.197 -> v1.0.201
Updating serde_json v1.0.115 -> v1.0.117
Updating socket2 v0.5.6 -> v0.5.7
Updating syn v2.0.58 -> v2.0.62
Updating sysinfo v0.30.8 -> v0.30.12
Updating thiserror v1.0.58 -> v1.0.60
Updating thiserror-impl v1.0.58 -> v1.0.60
Updating tokio-util v0.7.10 -> v0.7.11
Updating type-map v0.4.0 -> v0.5.0
Updating unic-langid v0.9.4 -> v0.9.5
Updating unic-langid-impl v0.9.4 -> v0.9.5
Updating unic-langid-macros v0.9.4 -> v0.9.5
Updating unic-langid-macros-impl v0.9.4 -> v0.9.5
Updating unicode-width v0.1.11 -> v0.1.12
Updating winapi-util v0.1.6 -> v0.1.8
Updating windows-targets v0.52.4 -> v0.52.5
Updating windows_aarch64_gnullvm v0.52.4 -> v0.52.5
Updating windows_aarch64_msvc v0.52.4 -> v0.52.5
Updating windows_i686_gnu v0.52.4 -> v0.52.5
Adding windows_i686_gnullvm v0.52.5
Updating windows_i686_msvc v0.52.4 -> v0.52.5
Updating windows_x86_64_gnu v0.52.4 -> v0.52.5
Updating windows_x86_64_gnullvm v0.52.4 -> v0.52.5
Updating windows_x86_64_msvc v0.52.4 -> v0.52.5
Updating zerocopy v0.7.32 -> v0.7.34
Updating zerocopy-derive v0.7.32 -> v0.7.34
note: pass `--verbose` to see 94 unchanged dependencies behind latest
```
|
|
|
|
Miri subtree update
r? `@ghost`
|
|
check if `x test tests` missing any test directory
Add a unit test to ensure we don't skip any test directories for `x test tests` in the future.
|
|
|
|
|
|
alloc: update comments around malloc() alignment
Also separate the C heap shims form the Windows heap shims; their guarantees aren't quite the same.
|
