[roll] Roll fuchsia [kernel][libc] Disallow global destructors outside kernel proper

The kernel proper has a no-op __cxa_atexit function and accepts
compiler-generated global destructors that just never get run.
This is OK since "program exit" is shutdown/reboot and the
important teardown work is all explicit.  The other kernel-like
contexts should be more strict since their "program exit" is
really hand-off to another program sharing their memory, and so
cannot easily assume that any destructor's work is something that
can be omitted safely.

Original-Fixed: 402588474
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1226624
Original-Revision: 877c9ecf12f979dcd0ea983220c84f609f218139
GitOrigin-RevId: 903f35f2e5a4106fabdff2073df162da054a7dbe
Change-Id: I55a06331182ce066dff0ad5cdf25a2389abce7f3
1 file changed
tree: b2cdf71c30611c482b8fc4ffa9ef83d8c474de59
  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.