[roll] Roll fuchsia [build][lto] Only support FatLTO for ELF targets with clang

Because we normally only enable LTO with the clang toolchain
when targeting ELF, it wasn't clear that other targets/toolchains
may sometimes receive FatLTO configs. This can happen when opting
targets out of FatLTO features, like the no-fat-lto-objects-linking
config. https://fxrev.dev/1121663 updates our test template to avoid
possible FatLTO linking when it is enabled, and thus exposed this
combination.

This patch opts GCC and non-ELF targets out of all FatLTO related
configs.

Original-Bug: 368146498, 364615885
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1121555
Original-Revision: 9eab015c586e821252405ddbf25762aef5d1bb40
GitOrigin-RevId: 5ec9a9c1288b86d130caad1c38024418abb253f1
Change-Id: I073b3faa9a3d7fd42417c2324496ca038bfd1313
1 file changed
tree: 1ae4415618c88907415d3218c04b2d8593c018e7
  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 in one of the communication channels documented at get involved.

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.