[roll] Roll fuchsia [dl] Introduce Module Unmapping

This CL unmaps the module's data when the Module data structure is
destroyed. This is usually performed when the module is unloaded by
`dlclose` but can also happen as part of the garbage collection process
during loading or at the conclusion of tests when the runtime dynamic
linker is torn down.

The implementation for dl::Unmap lives in separate TUs that get compiled
depending on the platform.

Original-Bug: 331468188
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1012878
Original-Revision: 919c475c102b9dc98fae262425867dd7cb9dba1c
GitOrigin-RevId: a0320b650664281439eb5fbba628e98e32a09136
Change-Id: I396f52bbf39442b3532b1f0c1bec81c71c25e334
1 file changed
tree: f764e35bb966477e520cf873df416af1a88aaa87
  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.