[roll] Roll fuchsia Revert "[build][rust] Workaround dropped RISC-V target features in LTO"

This reverts commit bf0a761ed46a099b1f312b88e8807f49f5ea980d.

Reason for revert: There needs to be more nuanced handling when passing `-mllvm` flags through Rust's `-Clink-args=` for various platform differences. We can reland when we're certain we handle those cases correctly.

Original change's description:
> [build][rust] Workaround dropped RISC-V target features in LTO
>
> While the clang and LLVM toolchains have a more robust handling of
> target features, the current intree Rust toolchain does not, meaning
> that its possible for the LTO'd modules in RISC-V to have missing target
> features, like setting the floating point ABI correctly.
>
> Original-Fixed: 339099402
> Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1045599

No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1046701
Original-Revision: 3ead44e17d4ee8a639e62fa24ccc079b02694bcb
GitOrigin-RevId: 54380f0fea82c82ee40357972c9bda8ddbf5ce06
Change-Id: I8759b1dfabb04d7e17e076905232f7c9e1d2385d
1 file changed
tree: 19d9467fd03fc2b0d825ad40432609486dc92911
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.