commit | 3cb6123cedec596d510f34a9d5f58e371091b0fa | [log] [tgz] |
---|---|---|
author | Roland McGrath <mcgrathr@google.com> | Fri Jun 15 15:17:09 2018 -0700 |
committer | Roland McGrath <mcgrathr@google.com> | Fri Jun 15 22:49:31 2018 +0000 |
tree | 7b27671f0b6bf4e10b759d7dbc1410197231994b | |
parent | 510d556c29b1580b2877d791e5610ce772942d5f [diff] |
[ulib][tftp] Fix invalid references to containing function constexprs from lambda Even constants that are actually just integrated at compile time technically need to be in a capture to be visible in a lambda when defined in a containing function scope. A lambda with captures cannot be converted into a function pointer, so captures can't be used here. Instead, the declarations need to be in a containing scope with permanent extent. Change-Id: I24474acd1b4bd42736f77c36394cea34bb0d9f3c
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.