[roll] Roll fuchsia [fuchsia-async] Some optimizations to AtomicFuture

1. Use fetch_and and fetch_or which might be faster.

2. Integrate `Notifier` with `AtomicFuture`; we don't need the two
   different atomic variables.

3. If a task is awoken whilst it is being polled, avoid adding it to a
   run queue, which can cause spinning on other threads.  We can add it
   to a run queue when it finishes being polled.

4. Save memory by eliminating `source` when not configured, and removing
   the `Option` in `AtomicFuture`.

Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1001076
Original-Revision: 17b0abf0f0abec9a465b9bdfe18188aa99acf048
GitOrigin-RevId: f8c06f4088d8c3f74b2b50b49ed12eb57c6c6b40
Change-Id: I61e73df931f81e30e6f23f4f39812d0acf20e281
1 file changed
tree: 2fda398db4eaaddbe35ee913be0603a5a59a0953
  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.