Add target support for RTEMS Arm by thesummer · Pull Request #127021 · rust-lang/rust (original) (raw)

rustbot added O-unix

Operating system: Unix-like

S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

T-bootstrap

Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

T-compiler

Relevant to the compiler team, which will review and decide on the PR/issue.

T-libs

Relevant to the library team, which will review and decide on the PR/issue.

labels

Jun 27, 2024

rustbot added S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

and removed S-waiting-on-author

Status: This is awaiting some action (such as code changes or more information) from the author.

labels

Sep 3, 2024

bors added S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

and removed S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

labels

Sep 3, 2024

GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request

Sep 3, 2024

…-rtems-arm-xilinx-zedboard, r=tgross35

Add target support for RTEMS Arm

armv7-rtems-eabihf

This PR adds a new target for the RTEMS RTOS. To get things started it focuses on Xilinx/AMD Zynq-based targets, but in theory it should also support other armv7-based board support packages in the future. Given that RTEMS has support for many POSIX functions it is mostly enabling corresponding unix features for the new target. I also previously started a PR in libc (rust-lang/libc#3561) to add the needed OS specific C-bindings and was told that a PR in this repo is needed first. I will update the PR to the newest version after approval here. I will probably also need to change one line in the backtrace repo.

Current status is that I could compile rustc for the new target locally (with the updated libc and backtrace) and could compile binaries, link, and execute a simple "Hello World" RTEMS application for the target hardware.

A proposed target or target-specific patch that substantially changes code shared with other targets (not just target-specific code) must be reviewed and approved by the appropriate team for that shared code before acceptance.

There should be no breaking changes for existing targets. Main changes are adding corresponding cfg switches for the RTEMS OS and adding the C binding in libc.

Tier 3 target 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 do the maintenance (for now) further members of the RTEMS community will most likely join once the first steps have been done.

• 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.
  • 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.

The proposed triple is armv7-rtems-eabihf

• 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 must not introduce license incompatibilities.
  • Anything added to the Rust repository must be under the standard Rust license (MIT OR Apache-2.0).
  • 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.
  • 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.
  • "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.

The tools consists of the cross-compiler toolchain (gcc-based). The RTEMS kernel (BSD license) and parts of the driver stack of FreeBSD (BSD license). All tools are FOSS and publicly available here: https://gitlab.rtems.org/rtems There are also no new features or dependencies introduced to the Rust code.

• 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.

N/A to me. I am not a reviewer nor Rust team member.

• 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.

core and std compile. Some advanced features of the std lib might not work yet. However, the goal of this tier 3 target it to make it easier for other people to build and run test applications to better identify the unsupported features and work towards enabling them.

• 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.

Building is described in platform support doc. Running simple unit tests works. Running the test suite of the stdlib is currently not that easy. Trying to work towards that after the this target has been added to the nightly.

• 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.

Understood.

- 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.

Ok

• 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.

I think, I didn't add any breaking changes for any existing targets (see the comment regarding features above).

• Tier 3 targets must be able to produce assembly using at least one of rustc's supported backends from any host target.

Can produce assembly code via the llvm backend (tested on Linux).

If a tier 3 target stops meeting these requirements, or the target maintainers no longer have interest or time, or the target shows no signs of activity and has not built for some time, or removing the target would improve the quality of the Rust codebase, we may post a PR to remove it; any such PR will be CCed to the target maintainers (and potentially other people who have previously worked on the target), to check potential interest in improving the situation.GIAt this tier, the Rust project provides no official support for a target, so we place minimal requirements on the introduction of targets.

Understood.

r? compiler-team

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 3, 2024

…llaumeGomez

Rollup of 7 pull requests

Successful merges:

• rust-lang#127021 (Add target support for RTEMS Arm)
• rust-lang#128871 (bypass linker configuration and cross target check for specific commands)
• rust-lang#129471 ([rustdoc] Sort impl associated items by kinds and then by appearance)
• rust-lang#129529 (Add test to build crates used by r-a on stable)
• rust-lang#129706 (Rename dump of coroutine by-move-body to be more consistent, fix ICE in dump_mir)
• rust-lang#129796 (Unify scraped examples with other code examples)
• rust-lang#129939 (explain why Rvalue::Len still exists)

r? @ghost @rustbot modify labels: rollup

tgross35 added a commit to tgross35/rust that referenced this pull request

Sep 4, 2024

…-rtems-arm-xilinx-zedboard, r=tgross35

Add target support for RTEMS Arm

armv7-rtems-eabihf

This PR adds a new target for the RTEMS RTOS. To get things started it focuses on Xilinx/AMD Zynq-based targets, but in theory it should also support other armv7-based board support packages in the future. Given that RTEMS has support for many POSIX functions it is mostly enabling corresponding unix features for the new target. I also previously started a PR in libc (rust-lang/libc#3561) to add the needed OS specific C-bindings and was told that a PR in this repo is needed first. I will update the PR to the newest version after approval here. I will probably also need to change one line in the backtrace repo.

Current status is that I could compile rustc for the new target locally (with the updated libc and backtrace) and could compile binaries, link, and execute a simple "Hello World" RTEMS application for the target hardware.

A proposed target or target-specific patch that substantially changes code shared with other targets (not just target-specific code) must be reviewed and approved by the appropriate team for that shared code before acceptance.

There should be no breaking changes for existing targets. Main changes are adding corresponding cfg switches for the RTEMS OS and adding the C binding in libc.

Tier 3 target 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 do the maintenance (for now) further members of the RTEMS community will most likely join once the first steps have been done.

• 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.
  • 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.

The proposed triple is armv7-rtems-eabihf

• 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 must not introduce license incompatibilities.
  • Anything added to the Rust repository must be under the standard Rust license (MIT OR Apache-2.0).
  • 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.
  • 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.
  • "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.

The tools consists of the cross-compiler toolchain (gcc-based). The RTEMS kernel (BSD license) and parts of the driver stack of FreeBSD (BSD license). All tools are FOSS and publicly available here: https://gitlab.rtems.org/rtems There are also no new features or dependencies introduced to the Rust code.

• 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.

N/A to me. I am not a reviewer nor Rust team member.

• 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.

core and std compile. Some advanced features of the std lib might not work yet. However, the goal of this tier 3 target it to make it easier for other people to build and run test applications to better identify the unsupported features and work towards enabling them.

• 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.

Building is described in platform support doc. Running simple unit tests works. Running the test suite of the stdlib is currently not that easy. Trying to work towards that after the this target has been added to the nightly.

• 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.

Understood.

- 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.

Ok

• 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.

I think, I didn't add any breaking changes for any existing targets (see the comment regarding features above).

• Tier 3 targets must be able to produce assembly using at least one of rustc's supported backends from any host target.

Can produce assembly code via the llvm backend (tested on Linux).

If a tier 3 target stops meeting these requirements, or the target maintainers no longer have interest or time, or the target shows no signs of activity and has not built for some time, or removing the target would improve the quality of the Rust codebase, we may post a PR to remove it; any such PR will be CCed to the target maintainers (and potentially other people who have previously worked on the target), to check potential interest in improving the situation.GIAt this tier, the Rust project provides no official support for a target, so we place minimal requirements on the introduction of targets.

Understood.

r? compiler-team

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 4, 2024

Rollup of 8 pull requests

Successful merges:

• rust-lang#101339 (enable -Zrandomize-layout in debug CI builds )
• rust-lang#127021 (Add target support for RTEMS Arm)
• rust-lang#128871 (bypass linker configuration and cross target check for specific commands)
• rust-lang#129471 ([rustdoc] Sort impl associated items by kinds and then by appearance)
• rust-lang#129529 (Add test to build crates used by r-a on stable)
• rust-lang#129624 (Adjust memchr pinning and run cargo update)
• rust-lang#129796 (Unify scraped examples with other code examples)
• rust-lang#129939 (explain why Rvalue::Len still exists)

r? @ghost @rustbot modify labels: rollup

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 4, 2024

Rollup of 8 pull requests

Successful merges:

• rust-lang#101339 (enable -Zrandomize-layout in debug CI builds )
• rust-lang#127021 (Add target support for RTEMS Arm)
• rust-lang#128871 (bypass linker configuration and cross target check for specific commands)
• rust-lang#129471 ([rustdoc] Sort impl associated items by kinds and then by appearance)
• rust-lang#129529 (Add test to build crates used by r-a on stable)
• rust-lang#129624 (Adjust memchr pinning and run cargo update)
• rust-lang#129796 (Unify scraped examples with other code examples)
• rust-lang#129939 (explain why Rvalue::Len still exists)

r? @ghost @rustbot modify labels: rollup

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 4, 2024

Rollup of 8 pull requests

Successful merges:

• rust-lang#101339 (enable -Zrandomize-layout in debug CI builds )
• rust-lang#127021 (Add target support for RTEMS Arm)
• rust-lang#128871 (bypass linker configuration and cross target check for specific commands)
• rust-lang#129471 ([rustdoc] Sort impl associated items by kinds and then by appearance)
• rust-lang#129529 (Add test to build crates used by r-a on stable)
• rust-lang#129624 (Adjust memchr pinning and run cargo update)
• rust-lang#129796 (Unify scraped examples with other code examples)
• rust-lang#129939 (explain why Rvalue::Len still exists)

r? @ghost @rustbot modify labels: rollup

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 5, 2024

Rollup of 8 pull requests

Successful merges:

• rust-lang#101339 (enable -Zrandomize-layout in debug CI builds )
• rust-lang#127021 (Add target support for RTEMS Arm)
• rust-lang#128871 (bypass linker configuration and cross target check for specific commands)
• rust-lang#129471 ([rustdoc] Sort impl associated items by kinds and then by appearance)
• rust-lang#129529 (Add test to build crates used by r-a on stable)
• rust-lang#129624 (Adjust memchr pinning and run cargo update)
• rust-lang#129796 (Unify scraped examples with other code examples)
• rust-lang#129939 (explain why Rvalue::Len still exists)

r? @ghost @rustbot modify labels: rollup

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 5, 2024

bors added a commit to rust-lang-ci/rust that referenced this pull request

Sep 5, 2024

rust-timer added a commit to rust-lang-ci/rust that referenced this pull request

Sep 5, 2024

Rollup merge of rust-lang#127021 - thesummer:1-add-target-support-for-rtems-arm-xilinx-zedboard, r=tgross35

Add target support for RTEMS Arm

armv7-rtems-eabihf

This PR adds a new target for the RTEMS RTOS. To get things started it focuses on Xilinx/AMD Zynq-based targets, but in theory it should also support other armv7-based board support packages in the future. Given that RTEMS has support for many POSIX functions it is mostly enabling corresponding unix features for the new target. I also previously started a PR in libc (rust-lang/libc#3561) to add the needed OS specific C-bindings and was told that a PR in this repo is needed first. I will update the PR to the newest version after approval here. I will probably also need to change one line in the backtrace repo.

Current status is that I could compile rustc for the new target locally (with the updated libc and backtrace) and could compile binaries, link, and execute a simple "Hello World" RTEMS application for the target hardware.

A proposed target or target-specific patch that substantially changes code shared with other targets (not just target-specific code) must be reviewed and approved by the appropriate team for that shared code before acceptance.

There should be no breaking changes for existing targets. Main changes are adding corresponding cfg switches for the RTEMS OS and adding the C binding in libc.

Tier 3 target 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 do the maintenance (for now) further members of the RTEMS community will most likely join once the first steps have been done.

• 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.
  • 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.

The proposed triple is armv7-rtems-eabihf

• 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 must not introduce license incompatibilities.
  • Anything added to the Rust repository must be under the standard Rust license (MIT OR Apache-2.0).
  • 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.
  • 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.
  • "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.

The tools consists of the cross-compiler toolchain (gcc-based). The RTEMS kernel (BSD license) and parts of the driver stack of FreeBSD (BSD license). All tools are FOSS and publicly available here: https://gitlab.rtems.org/rtems There are also no new features or dependencies introduced to the Rust code.

• 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.

N/A to me. I am not a reviewer nor Rust team member.

• 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.

core and std compile. Some advanced features of the std lib might not work yet. However, the goal of this tier 3 target it to make it easier for other people to build and run test applications to better identify the unsupported features and work towards enabling them.

• 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.

Building is described in platform support doc. Running simple unit tests works. Running the test suite of the stdlib is currently not that easy. Trying to work towards that after the this target has been added to the nightly.

• 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.

Understood.

- 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.

Ok

• 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.

I think, I didn't add any breaking changes for any existing targets (see the comment regarding features above).

• Tier 3 targets must be able to produce assembly using at least one of rustc's supported backends from any host target.

Can produce assembly code via the llvm backend (tested on Linux).

If a tier 3 target stops meeting these requirements, or the target maintainers no longer have interest or time, or the target shows no signs of activity and has not built for some time, or removing the target would improve the quality of the Rust codebase, we may post a PR to remove it; any such PR will be CCed to the target maintainers (and potentially other people who have previously worked on the target), to check potential interest in improving the situation.GIAt this tier, the Rust project provides no official support for a target, so we place minimal requirements on the introduction of targets.

Understood.

r? compiler-team

workingjubilee pushed a commit to rust-lang/backtrace-rs that referenced this pull request

Sep 7, 2024

We added target support for RTEMS OS in rust-lang/rust#127021

It has a POSIX interface, so we could reuse much of the unix backend, but currently libunwind is not supported.

Add a cfg switch to disable libunwind for RTEMS.

This was referenced

Oct 15, 2024

cuviper added the relnotes

Marks issues that should be documented in the release notes of the next release.

label

Nov 21, 2024

wip-sync pushed a commit to NetBSD/pkgsrc-wip that referenced this pull request

Nov 30, 2024

Pkgsrc changes compared to rust182:

• Remove patches related to rust-lang/rust#130110, which is now integrated upstream.
• Remove patch to vendor/cc-1.0.79, now integrated in the current vendored cc crate.
• Checksum updates.

TODO:

• Cross-compilation fails ref. rust-lang/rust#133629

Upstream changes:

Version 1.83.0 (2024-11-28)

Language

• [Stabilize &mut, *mut, &Cell, and *const Cell in const.] (rust-lang/rust#129195)
• [Allow creating references to statics in const initializers.] (rust-lang/rust#129759)
• [Implement raw lifetimes and labels ('r#ident).] (rust-lang/rust#126452)
• [Define behavior when atomic and non-atomic reads race.] (rust-lang/rust#128778)
• [Non-exhaustive structs may now be empty.] (rust-lang/rust#128934)
• [Disallow implicit coercions from places of type !] (rust-lang/rust#129392)
• [const extern functions can now be defined for other calling conventions.] (rust-lang/rust#129753)
• [Stabilize expr_2021 macro fragment specifier in all editions.] (rust-lang/rust#129972)
• [The non_local_definitions lint now fires on less code and warns by default.] (rust-lang/rust#127117)

Compiler

• [Deprecate unsound -Csoft-float flag.] (rust-lang/rust#129897)
• Add many new tier 3 targets:
  • [aarch64_unknown_nto_qnx700] (rust-lang/rust#127897)
  • [arm64e-apple-tvos] (rust-lang/rust#130614)
  • [armv7-rtems-eabihf] (rust-lang/rust#127021)
  • [loongarch64-unknown-linux-ohos] (rust-lang/rust#130750)
  • [riscv32-wrs-vxworks and riscv64-wrs-vxworks] (rust-lang/rust#130549)
  • [riscv32{e|em|emc}-unknown-none-elf] (rust-lang/rust#130555)
  • [x86_64-unknown-hurd-gnu] (rust-lang/rust#128345)
  • [x86_64-unknown-trusty] (rust-lang/rust#130453)

Refer to Rust's [platform support page][platform-support-doc] for more information on Rust's tiered platform support.

Libraries

• [Implement PartialEq for ExitCode.] (rust-lang/rust#127633)
• [Document that catch_unwind can deal with foreign exceptions without UB, although the exact behavior is unspecified.] (rust-lang/rust#128321)
• [Implement Default for HashMap/HashSet iterators that don't already have it.] (rust-lang/rust#128711)
• [Bump Unicode to version 16.0.0.] (rust-lang/rust#130183)
• [Change documentation of ptr::add/sub to not claim equivalence with offset.] (rust-lang/rust#130229).

Stabilized APIs

• [BufRead::skip_until] (https://doc.rust-lang.org/stable/std/io/trait.BufRead.html#method.skip_until)
• [ControlFlow::break_value] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.break_value)
• [ControlFlow::continue_value] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.continue_value)
• [ControlFlow::map_break] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.map_break)
• [ControlFlow::map_continue] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.map_continue)
• [DebugList::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugList.html#method.finish_non_exhaustive)
• [DebugMap::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugMap.html#method.finish_non_exhaustive)
• [DebugSet::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugSet.html#method.finish_non_exhaustive)
• [DebugTuple::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugTuple.html#method.finish_non_exhaustive)
• [ErrorKind::ArgumentListTooLong] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ArgumentListTooLong)
• [ErrorKind::Deadlock] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.Deadlock)
• [ErrorKind::DirectoryNotEmpty] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.DirectoryNotEmpty)
• [ErrorKind::ExecutableFileBusy] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ExecutableFileBusy)
• [ErrorKind::FileTooLarge] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.FileTooLarge)
• [ErrorKind::HostUnreachable] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.HostUnreachable)
• [ErrorKind::IsADirectory] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.IsADirectory)
• [ErrorKind::NetworkDown] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NetworkDown)
• [ErrorKind::NetworkUnreachable] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NetworkUnreachable)
• [ErrorKind::NotADirectory] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NotADirectory)
• [ErrorKind::NotSeekable] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NotSeekable)
• [ErrorKind::ReadOnlyFilesystem] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ReadOnlyFilesystem)
• [ErrorKind::ResourceBusy] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ResourceBusy)
• [ErrorKind::StaleNetworkFileHandle] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.StaleNetworkFileHandle)
• [ErrorKind::StorageFull] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.StorageFull)
• [ErrorKind::TooManyLinks] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.TooManyLinks)
• [Option::get_or_insert_default] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.get_or_insert_default)
• [Waker::data] (https://doc.rust-lang.org/stable/core/task/struct.Waker.html#method.data)
• [Waker::new] (https://doc.rust-lang.org/stable/core/task/struct.Waker.html#method.new)
• [Waker::vtable] (https://doc.rust-lang.org/stable/core/task/struct.Waker.html#method.vtable)
• [char::MIN] (https://doc.rust-lang.org/stable/core/primitive.char.html#associatedconstant.MIN)
• [hash_map::Entry::insert_entry] (https://doc.rust-lang.org/stable/std/collections/hash_map/enum.Entry.html#method.insert_entry)
• [hash_map::VacantEntry::insert_entry] (https://doc.rust-lang.org/stable/std/collections/hash_map/struct.VacantEntry.html#method.insert_entry)

These APIs are now stable in const contexts:

• [Cell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.Cell.html#method.into_inner)
• [Duration::as_secs_f32] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.as_secs_f32)
• [Duration::as_secs_f64] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.as_secs_f64)
• [Duration::div_duration_f32] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.div_duration_f32)
• [Duration::div_duration_f64] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.div_duration_f64)
• [MaybeUninit::as_mut_ptr] (https://doc.rust-lang.org/stable/core/mem/union.MaybeUninit.html#method.as_mut_ptr)
• [NonNull::as_mut] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.as_mut)
• [NonNull::copy_from] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_from)
• [NonNull::copy_from_nonoverlapping] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_from_nonoverlapping)
• [NonNull::copy_to] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_to)
• [NonNull::copy_to_nonoverlapping] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_to_nonoverlapping)
• [NonNull::slice_from_raw_parts] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.slice_from_raw_parts)
• [NonNull::write] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.write)
• [NonNull::write_bytes] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.write_bytes)
• [NonNull::write_unaligned] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.write_unaligned)
• [OnceCell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.OnceCell.html#method.into_inner)
• [Option::as_mut] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.as_mut)
• [Option::expect] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.expect)
• [Option::replace] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.replace)
• [Option::take] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.take)
• [Option::unwrap] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.unwrap)
• [Option::unwrap_unchecked] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.unwrap_unchecked)
• [Option::<&_>::copied] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.copied)
• [Option::<&mut _>::copied] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.copied-1)
• [Option::<Option<_>>::flatten] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.flatten)
• [Option::<Result<_, _>>::transpose] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.transpose)
• [RefCell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.RefCell.html#method.into_inner)
• [Result::as_mut] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.as_mut)
• [Result::<&_, _>::copied] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.copied)
• [Result::<&mut _, _>::copied] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.copied-1)
• [Result::<Option<_>, _>::transpose] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.transpose)
• [UnsafeCell::get_mut] (https://doc.rust-lang.org/stable/core/cell/struct.UnsafeCell.html#method.get_mut)
• [UnsafeCell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.UnsafeCell.html#method.into_inner)
• [array::from_mut] (https://doc.rust-lang.org/stable/core/array/fn.from_mut.html)
• [char::encode_utf8] (https://doc.rust-lang.org/stable/core/primitive.char.html#method.encode_utf8)
• [{float}::classify] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.classify)
• [{float}::is_finite] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_finite)
• [{float}::is_infinite] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_infinite)
• [{float}::is_nan] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_nan)
• [{float}::is_normal] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_normal)
• [{float}::is_sign_negative] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_sign_negative)
• [{float}::is_sign_positive] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_sign_positive)
• [{float}::is_subnormal] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_subnormal)
• [{float}::from_bits] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_bits)
• [{float}::from_be_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_be_bytes)
• [{float}::from_le_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_le_bytes)
• [{float}::from_ne_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_ne_bytes)
• [{float}::to_bits] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_bits)
• [{float}::to_be_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_be_bytes)
• [{float}::to_le_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_le_bytes)
• [{float}::to_ne_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_ne_bytes)
• [mem::replace] (https://doc.rust-lang.org/stable/core/mem/fn.replace.html)
• [ptr::replace] (https://doc.rust-lang.org/stable/core/ptr/fn.replace.html)
• [ptr::slice_from_raw_parts_mut] (https://doc.rust-lang.org/stable/core/ptr/fn.slice_from_raw_parts_mut.html)
• [ptr::write] (https://doc.rust-lang.org/stable/core/ptr/fn.write.html)
• [ptr::write_unaligned] (https://doc.rust-lang.org/stable/core/ptr/fn.write_unaligned.html)
• [<*const _>::copy_to] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to)
• [<*const _>::copy_to_nonoverlapping] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to_nonoverlapping)
• [<*mut _>::copy_from] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_from)
• [<*mut _>::copy_from_nonoverlapping] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_from_nonoverlapping)
• [<*mut _>::copy_to] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to-1)
• [<*mut _>::copy_to_nonoverlapping] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to_nonoverlapping-1)
• [<*mut _>::write] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.write)
• [<*mut _>::write_bytes] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.write_bytes)
• [<*mut _>::write_unaligned] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.write_unaligned)
• [slice::from_mut] (https://doc.rust-lang.org/stable/core/slice/fn.from_mut.html)
• [slice::from_raw_parts_mut] (https://doc.rust-lang.org/stable/core/slice/fn.from_raw_parts_mut.html)
• [<[_]>::first_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.first_mut)
• [<[_]>::last_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.last_mut)
• [<[_]>::first_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.first_chunk_mut)
• [<[_]>::last_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.last_chunk_mut)
• [<[_]>::split_at_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_at_mut)
• [<[_]>::split_at_mut_checked] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_at_mut_checked)
• [<[_]>::split_at_mut_unchecked] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_at_mut_unchecked)
• [<[_]>::split_first_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_first_mut)
• [<[_]>::split_last_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_last_mut)
• [<[_]>::split_first_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_first_chunk_mut)
• [<[_]>::split_last_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_last_chunk_mut)
• [str::as_bytes_mut] (https://doc.rust-lang.org/stable/core/primitive.str.html#method.as_bytes_mut)
• [str::as_mut_ptr] (https://doc.rust-lang.org/stable/core/primitive.str.html#method.as_mut_ptr)
• [str::from_utf8_unchecked_mut] (https://doc.rust-lang.org/stable/core/str/fn.from_utf8_unchecked_mut.html)

Cargo

• [Introduced a new CARGO_MANIFEST_PATH environment variable, similar to CARGO_MANIFEST_DIR but pointing directly to the manifest file.] (rust-lang/cargo#14404)
• [Added package.autolib to the manifest, allowing [lib] auto-discovery to be disabled.] (rust-lang/cargo#14591)
• [Declare support level for each crate in Cargo's Charter / crate docs.] (rust-lang/cargo#14600)
• [Declare new Intentional Artifacts as 'small' changes.] (rust-lang/cargo#14599)

Rustdoc

• [The sidebar / hamburger menu table of contents now includes the # headers from the main item's doc comment] (rust-lang/rust#120736). This is similar to a third-party feature provided by the rustdoc-search-enhancements browser extension.

Compatibility Notes

• [Warn against function pointers using unsupported ABI strings.] (rust-lang/rust#128784)

• [Check well-formedness of the source type's signature in fn pointer casts.] (rust-lang/rust#129021) This partly closes a soundness hole that comes when casting a function item to function pointer

• [Use equality instead of subtyping when resolving type dependent paths.] (rust-lang/rust#129073)

• Linking on macOS now correctly includes Rust's default deployment target. Due to a linker bug, you might have to pass MACOSX_DEPLOYMENT_TARGET or fix your #[link] attributes to point to the correct frameworks. See <rust-lang/rust#129369>.

• [Rust will now correctly raise an error for repr(Rust) written on non-struct/enum/union items, since it previous did not have any effect.] (rust-lang/rust#129422)

• The future incompatibility lint deprecated_cfg_attr_crate_type_name [has been made into a hard error] (rust-lang/rust#129670). It was used to deny usage of #![crate_type] and #![crate_name] attributes in #![cfg_attr], which required a hack in the compiler to be able to change the used crate type and crate name after cfg expansion. Users can use --crate-type instead of #![cfg_attr(..., crate_type = "...")] and --crate-name instead of #![cfg_attr(..., crate_name = "...")] when running rustc/cargo rustc on the command line. Use of those two attributes outside of #![cfg_attr] continue to be fully supported.

• Until now, paths into the sysroot were always prefixed with /rustc/$hash in diagnostics, codegen, backtrace, e.g.

  thread 'main' panicked at 'hello world', map-panic.rs:2:50
  stack backtrace:
     0: std::panicking::begin_panic
               at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:616:12
     1: map_panic::main::{{closure}}
               at ./map-panic.rs:2:50
     2: core::option::Option<T>::map
               at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/option.rs:929:29
     3: map_panic::main
               at ./map-panic.rs:2:30
     4: core::ops::function::FnOnce::call_once
               at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/ops/function.rs:248:5
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

  [RFC 3127 said] (https://rust-lang.github.io/rfcs/3127-trim-paths.html#changing-handling-of-sysroot-path-in-rustc)

  We want to change this behaviour such that, when rust-src source files can be discovered, the virtual path is discarded and therefore the local path will be embedded, unless there is a --remap-path-prefix that causes this local path to be remapped in the usual way.

  #129687 implements this behaviour, when rust-src is present at compile time, rustc replaces /rustc/$hash with a real path into the local rust-src component with best effort. To sanitize this, users must explicitly supply --remap-path-prefix=<path to rust-src>=foo or not have the rust-src component installed.

• The allow-by-default missing_docs lint used to disable itself when invoked through rustc --test/cargo test, resulting in #[expect(missing_docs)] emitting false positives due to the expectation being wrongly unfulfilled. This behavior [has now been removed] (rust-lang/rust#130025), which allows #[expect(missing_docs)] to be fulfilled in all scenarios, but will also report new missing_docs diagnostics for publicly reachable #[cfg(test)] items, [integration test] (https://doc.rust-lang.org/cargo/reference/cargo-targets.html#integration-tests) crate-level documentation, and publicly reachable items in integration tests.

• [The armv8r-none-eabihf target now uses the Armv8-R required set of floating-point features.] (rust-lang/rust#130295)

• [Fix a soundness bug where rustc wouldn't detect unconstrained higher-ranked lifetimes in a dyn Trait's associated types that occur due to supertraits.] (rust-lang/rust#130367)

• [Update the minimum external LLVM version to 18.] (rust-lang/rust#130487)

• [Remove aarch64-fuchsia and x86_64-fuchsia target aliases in favor of aarch64-unknown-fuchsia and x86_64-unknown-fuchsia respectively.] (rust-lang/rust#130657)

• [The ABI-level exception class of a Rust panic is now encoded with native-endian bytes, so it is legible in hex dumps.] (rust-lang/rust#130897)

• [Visual Studio 2013 is no longer supported for MSVC targets.] (rust-lang/rust#131070)

• [The sysroot no longer contains the std dynamic library in its top-level lib/ dir.] (rust-lang/rust#131188)

tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request

Dec 5, 2024

This MR contains the following updates:

MR created with the help of el-capitano/tools/renovate-bot.

Proposed changes to behavior should be submitted there as MRs.

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

• If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request

Feb 24, 2025

Pkgsrc changes:

• Introduce use of TOOL* settings.
• On NetBSD, use patchelf in the install phase to fix up RPATHs.
• Reduce verbosity by dropping -v flag to x.py invocations.
• Remove patches related to rust-lang/rust#130110, which is now integrated upstream.
• Remove patch to vendor/cc-1.0.79, now integrated in the current vendored cc crate.
• Checksum updates.

Upstream changes:

Version 1.83.0 (2024-11-28)

Language

• [Stabilize &mut, *mut, &Cell, and *const Cell in const.] (rust-lang/rust#129195)
• [Allow creating references to statics in const initializers.] (rust-lang/rust#129759)
• [Implement raw lifetimes and labels ('r#ident).] (rust-lang/rust#126452)
• [Define behavior when atomic and non-atomic reads race.] (rust-lang/rust#128778)
• [Non-exhaustive structs may now be empty.] (rust-lang/rust#128934)
• [Disallow implicit coercions from places of type !] (rust-lang/rust#129392)
• [const extern functions can now be defined for other calling conventions.] (rust-lang/rust#129753)
• [Stabilize expr_2021 macro fragment specifier in all editions.] (rust-lang/rust#129972)
• [The non_local_definitions lint now fires on less code and warns by default.] (rust-lang/rust#127117)

Compiler

• [Deprecate unsound -Csoft-float flag.] (rust-lang/rust#129897)
• Add many new tier 3 targets:
  • [aarch64_unknown_nto_qnx700] (rust-lang/rust#127897)
  • [arm64e-apple-tvos] (rust-lang/rust#130614)
  • [armv7-rtems-eabihf] (rust-lang/rust#127021)
  • [loongarch64-unknown-linux-ohos] (rust-lang/rust#130750)
  • [riscv32-wrs-vxworks and riscv64-wrs-vxworks] (rust-lang/rust#130549)
  • [riscv32{e|em|emc}-unknown-none-elf] (rust-lang/rust#130555)
  • [x86_64-unknown-hurd-gnu] (rust-lang/rust#128345)
  • [x86_64-unknown-trusty] (rust-lang/rust#130453)

Refer to Rust's [platform support page][platform-support-doc] for more information on Rust's tiered platform support.

Libraries

• [Implement PartialEq for ExitCode.] (rust-lang/rust#127633)
• [Document that catch_unwind can deal with foreign exceptions without UB, although the exact behavior is unspecified.] (rust-lang/rust#128321)
• [Implement Default for HashMap/HashSet iterators that don't already have it.] (rust-lang/rust#128711)
• [Bump Unicode to version 16.0.0.] (rust-lang/rust#130183)
• [Change documentation of ptr::add/sub to not claim equivalence with offset.] (rust-lang/rust#130229).

Stabilized APIs

• [BufRead::skip_until] (https://doc.rust-lang.org/stable/std/io/trait.BufRead.html#method.skip_until)
• [ControlFlow::break_value] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.break_value)
• [ControlFlow::continue_value] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.continue_value)
• [ControlFlow::map_break] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.map_break)
• [ControlFlow::map_continue] (https://doc.rust-lang.org/stable/core/ops/enum.ControlFlow.html#method.map_continue)
• [DebugList::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugList.html#method.finish_non_exhaustive)
• [DebugMap::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugMap.html#method.finish_non_exhaustive)
• [DebugSet::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugSet.html#method.finish_non_exhaustive)
• [DebugTuple::finish_non_exhaustive] (https://doc.rust-lang.org/stable/core/fmt/struct.DebugTuple.html#method.finish_non_exhaustive)
• [ErrorKind::ArgumentListTooLong] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ArgumentListTooLong)
• [ErrorKind::Deadlock] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.Deadlock)
• [ErrorKind::DirectoryNotEmpty] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.DirectoryNotEmpty)
• [ErrorKind::ExecutableFileBusy] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ExecutableFileBusy)
• [ErrorKind::FileTooLarge] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.FileTooLarge)
• [ErrorKind::HostUnreachable] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.HostUnreachable)
• [ErrorKind::IsADirectory] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.IsADirectory)
• [ErrorKind::NetworkDown] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NetworkDown)
• [ErrorKind::NetworkUnreachable] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NetworkUnreachable)
• [ErrorKind::NotADirectory] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NotADirectory)
• [ErrorKind::NotSeekable] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.NotSeekable)
• [ErrorKind::ReadOnlyFilesystem] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ReadOnlyFilesystem)
• [ErrorKind::ResourceBusy] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.ResourceBusy)
• [ErrorKind::StaleNetworkFileHandle] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.StaleNetworkFileHandle)
• [ErrorKind::StorageFull] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.StorageFull)
• [ErrorKind::TooManyLinks] (https://doc.rust-lang.org/stable/std/io/enum.ErrorKind.html#variant.TooManyLinks)
• [Option::get_or_insert_default] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.get_or_insert_default)
• [Waker::data] (https://doc.rust-lang.org/stable/core/task/struct.Waker.html#method.data)
• [Waker::new] (https://doc.rust-lang.org/stable/core/task/struct.Waker.html#method.new)
• [Waker::vtable] (https://doc.rust-lang.org/stable/core/task/struct.Waker.html#method.vtable)
• [char::MIN] (https://doc.rust-lang.org/stable/core/primitive.char.html#associatedconstant.MIN)
• [hash_map::Entry::insert_entry] (https://doc.rust-lang.org/stable/std/collections/hash_map/enum.Entry.html#method.insert_entry)
• [hash_map::VacantEntry::insert_entry] (https://doc.rust-lang.org/stable/std/collections/hash_map/struct.VacantEntry.html#method.insert_entry)

These APIs are now stable in const contexts:

• [Cell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.Cell.html#method.into_inner)
• [Duration::as_secs_f32] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.as_secs_f32)
• [Duration::as_secs_f64] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.as_secs_f64)
• [Duration::div_duration_f32] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.div_duration_f32)
• [Duration::div_duration_f64] (https://doc.rust-lang.org/stable/core/time/struct.Duration.html#method.div_duration_f64)
• [MaybeUninit::as_mut_ptr] (https://doc.rust-lang.org/stable/core/mem/union.MaybeUninit.html#method.as_mut_ptr)
• [NonNull::as_mut] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.as_mut)
• [NonNull::copy_from] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_from)
• [NonNull::copy_from_nonoverlapping] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_from_nonoverlapping)
• [NonNull::copy_to] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_to)
• [NonNull::copy_to_nonoverlapping] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.copy_to_nonoverlapping)
• [NonNull::slice_from_raw_parts] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.slice_from_raw_parts)
• [NonNull::write] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.write)
• [NonNull::write_bytes] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.write_bytes)
• [NonNull::write_unaligned] (https://doc.rust-lang.org/stable/core/ptr/struct.NonNull.html#method.write_unaligned)
• [OnceCell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.OnceCell.html#method.into_inner)
• [Option::as_mut] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.as_mut)
• [Option::expect] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.expect)
• [Option::replace] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.replace)
• [Option::take] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.take)
• [Option::unwrap] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.unwrap)
• [Option::unwrap_unchecked] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.unwrap_unchecked)
• [Option::<&_>::copied] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.copied)
• [Option::<&mut _>::copied] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.copied-1)
• [Option::<Option<_>>::flatten] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.flatten)
• [Option::<Result<_, _>>::transpose] (https://doc.rust-lang.org/stable/core/option/enum.Option.html#method.transpose)
• [RefCell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.RefCell.html#method.into_inner)
• [Result::as_mut] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.as_mut)
• [Result::<&_, _>::copied] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.copied)
• [Result::<&mut _, _>::copied] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.copied-1)
• [Result::<Option<_>, _>::transpose] (https://doc.rust-lang.org/stable/core/result/enum.Result.html#method.transpose)
• [UnsafeCell::get_mut] (https://doc.rust-lang.org/stable/core/cell/struct.UnsafeCell.html#method.get_mut)
• [UnsafeCell::into_inner] (https://doc.rust-lang.org/stable/core/cell/struct.UnsafeCell.html#method.into_inner)
• [array::from_mut] (https://doc.rust-lang.org/stable/core/array/fn.from_mut.html)
• [char::encode_utf8] (https://doc.rust-lang.org/stable/core/primitive.char.html#method.encode_utf8)
• [{float}::classify] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.classify)
• [{float}::is_finite] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_finite)
• [{float}::is_infinite] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_infinite)
• [{float}::is_nan] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_nan)
• [{float}::is_normal] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_normal)
• [{float}::is_sign_negative] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_sign_negative)
• [{float}::is_sign_positive] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_sign_positive)
• [{float}::is_subnormal] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.is_subnormal)
• [{float}::from_bits] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_bits)
• [{float}::from_be_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_be_bytes)
• [{float}::from_le_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_le_bytes)
• [{float}::from_ne_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.from_ne_bytes)
• [{float}::to_bits] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_bits)
• [{float}::to_be_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_be_bytes)
• [{float}::to_le_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_le_bytes)
• [{float}::to_ne_bytes] (https://doc.rust-lang.org/stable/core/primitive.f64.html#method.to_ne_bytes)
• [mem::replace] (https://doc.rust-lang.org/stable/core/mem/fn.replace.html)
• [ptr::replace] (https://doc.rust-lang.org/stable/core/ptr/fn.replace.html)
• [ptr::slice_from_raw_parts_mut] (https://doc.rust-lang.org/stable/core/ptr/fn.slice_from_raw_parts_mut.html)
• [ptr::write] (https://doc.rust-lang.org/stable/core/ptr/fn.write.html)
• [ptr::write_unaligned] (https://doc.rust-lang.org/stable/core/ptr/fn.write_unaligned.html)
• [<*const _>::copy_to] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to)
• [<*const _>::copy_to_nonoverlapping] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to_nonoverlapping)
• [<*mut _>::copy_from] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_from)
• [<*mut _>::copy_from_nonoverlapping] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_from_nonoverlapping)
• [<*mut _>::copy_to] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to-1)
• [<*mut _>::copy_to_nonoverlapping] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.copy_to_nonoverlapping-1)
• [<*mut _>::write] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.write)
• [<*mut _>::write_bytes] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.write_bytes)
• [<*mut _>::write_unaligned] (https://doc.rust-lang.org/stable/core/primitive.pointer.html#method.write_unaligned)
• [slice::from_mut] (https://doc.rust-lang.org/stable/core/slice/fn.from_mut.html)
• [slice::from_raw_parts_mut] (https://doc.rust-lang.org/stable/core/slice/fn.from_raw_parts_mut.html)
• [<[_]>::first_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.first_mut)
• [<[_]>::last_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.last_mut)
• [<[_]>::first_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.first_chunk_mut)
• [<[_]>::last_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.last_chunk_mut)
• [<[_]>::split_at_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_at_mut)
• [<[_]>::split_at_mut_checked] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_at_mut_checked)
• [<[_]>::split_at_mut_unchecked] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_at_mut_unchecked)
• [<[_]>::split_first_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_first_mut)
• [<[_]>::split_last_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_last_mut)
• [<[_]>::split_first_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_first_chunk_mut)
• [<[_]>::split_last_chunk_mut] (https://doc.rust-lang.org/stable/core/primitive.slice.html#method.split_last_chunk_mut)
• [str::as_bytes_mut] (https://doc.rust-lang.org/stable/core/primitive.str.html#method.as_bytes_mut)
• [str::as_mut_ptr] (https://doc.rust-lang.org/stable/core/primitive.str.html#method.as_mut_ptr)
• [str::from_utf8_unchecked_mut] (https://doc.rust-lang.org/stable/core/str/fn.from_utf8_unchecked_mut.html)

Cargo

• [Introduced a new CARGO_MANIFEST_PATH environment variable, similar to CARGO_MANIFEST_DIR but pointing directly to the manifest file.] (rust-lang/cargo#14404)
• [Added package.autolib to the manifest, allowing [lib] auto-discovery to be disabled.] (rust-lang/cargo#14591)
• [Declare support level for each crate in Cargo's Charter / crate docs.] (rust-lang/cargo#14600)
• [Declare new Intentional Artifacts as 'small' changes.] (rust-lang/cargo#14599)

Rustdoc

• [The sidebar / hamburger menu table of contents now includes the # headers from the main item's doc comment] (rust-lang/rust#120736). This is similar to a third-party feature provided by the rustdoc-search-enhancements browser extension.

Compatibility Notes

• [Warn against function pointers using unsupported ABI strings.] (rust-lang/rust#128784)

• [Check well-formedness of the source type's signature in fn pointer casts.] (rust-lang/rust#129021) This partly closes a soundness hole that comes when casting a function item to function pointer

• [Use equality instead of subtyping when resolving type dependent paths.] (rust-lang/rust#129073)

• Linking on macOS now correctly includes Rust's default deployment target. Due to a linker bug, you might have to pass MACOSX_DEPLOYMENT_TARGET or fix your #[link] attributes to point to the correct frameworks. See <rust-lang/rust#129369>.

• [Rust will now correctly raise an error for repr(Rust) written on non-struct/enum/union items, since it previous did not have any effect.] (rust-lang/rust#129422)

• The future incompatibility lint deprecated_cfg_attr_crate_type_name [has been made into a hard error] (rust-lang/rust#129670). It was used to deny usage of #![crate_type] and #![crate_name] attributes in #![cfg_attr], which required a hack in the compiler to be able to change the used crate type and crate name after cfg expansion. Users can use --crate-type instead of #![cfg_attr(..., crate_type = "...")] and --crate-name instead of #![cfg_attr(..., crate_name = "...")] when running rustc/cargo rustc on the command line. Use of those two attributes outside of #![cfg_attr] continue to be fully supported.

• Until now, paths into the sysroot were always prefixed with /rustc/$hash in diagnostics, codegen, backtrace, e.g.

  thread 'main' panicked at 'hello world', map-panic.rs:2:50
  stack backtrace:
     0: std::panicking::begin_panic
               at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:616:12
     1: map_panic::main::{{closure}}
               at ./map-panic.rs:2:50
     2: core::option::Option<T>::map
               at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/option.rs:929:29
     3: map_panic::main
               at ./map-panic.rs:2:30
     4: core::ops::function::FnOnce::call_once
               at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/ops/function.rs:248:5
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

  [RFC 3127 said] (https://rust-lang.github.io/rfcs/3127-trim-paths.html#changing-handling-of-sysroot-path-in-rustc)

  We want to change this behaviour such that, when rust-src source files can be discovered, the virtual path is discarded and therefore the local path will be embedded, unless there is a --remap-path-prefix that causes this local path to be remapped in the usual way.

  #129687 implements this behaviour, when rust-src is present at compile time, rustc replaces /rustc/$hash with a real path into the local rust-src component with best effort. To sanitize this, users must explicitly supply --remap-path-prefix=<path to rust-src>=foo or not have the rust-src component installed.

• The allow-by-default missing_docs lint used to disable itself when invoked through rustc --test/cargo test, resulting in #[expect(missing_docs)] emitting false positives due to the expectation being wrongly unfulfilled. This behavior [has now been removed] (rust-lang/rust#130025), which allows #[expect(missing_docs)] to be fulfilled in all scenarios, but will also report new missing_docs diagnostics for publicly reachable #[cfg(test)] items, [integration test] (https://doc.rust-lang.org/cargo/reference/cargo-targets.html#integration-tests) crate-level documentation, and publicly reachable items in integration tests.

• [The armv8r-none-eabihf target now uses the Armv8-R required set of floating-point features.] (rust-lang/rust#130295)

• [Fix a soundness bug where rustc wouldn't detect unconstrained higher-ranked lifetimes in a dyn Trait's associated types that occur due to supertraits.] (rust-lang/rust#130367)

• [Update the minimum external LLVM version to 18.] (rust-lang/rust#130487)

• [Remove aarch64-fuchsia and x86_64-fuchsia target aliases in favor of aarch64-unknown-fuchsia and x86_64-unknown-fuchsia respectively.] (rust-lang/rust#130657)

• [The ABI-level exception class of a Rust panic is now encoded with native-endian bytes, so it is legible in hex dumps.] (rust-lang/rust#130897)

• [Visual Studio 2013 is no longer supported for MSVC targets.] (rust-lang/rust#131070)

• [The sysroot no longer contains the std dynamic library in its top-level lib/ dir.] (rust-lang/rust#131188)