| commit | 688177673855a48d662517eb7bd0848d91b2b988 | [log] [tgz] |
|---|---|---|
| author | Pascal Perez <pascallouis@google.com> | Tue Dec 11 16:54:21 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Jan 27 19:52:53 2019 +0000 |
| tree | f8327cc5223d423f06f8d635097c6332d6027d72 | |
| parent | bca77f6bdb65d642bb812f8111bc47d71d0b0b99 [diff] |
[fidlc] Deferring Type Construction Post Raw to Flat Conversion
Introducing a generic representation named TypeConstructor to capture
all areas where we reference types. This makes it possible to have a
single representation, share code around it, and most importantly, defer
type construction to a later stage in the compiler, once all constants
have been resolved.
For instance, with the example:
const uint32 MAX_SIZE = 1024;
struct MyStruct {
string:MAX_SIZE desc;
string:1024 other_desc;
};
We must first resolve the MAX_SIZE constant to understand that the type
for both desc field, and other_desc field are the same.
Type constructors create types using type templates, which are looked up
by name. So for instance, the name "uint32" looks up a type template,
which is an instance of PrimitiveTypeTemplate, and which knows how to
instantiate a PrimitiveType representing a uint32.
All this machinery moves us closer to 1. canonicalizing types (because
their creation is now centralized, and soon easy to memoize), and 2.
introducing user-defined templates such as
struct pair<L, R> { ....
Which would get materialized dynamically.
This also makes it natural to extend type aliasing to use any types, not
just primitives.
Test: make tools -j12 HOST_USE_ASAN=true && ./build-x64/host_tests/fidl-compiler-test
Change-Id: Id97c6751b8944b5ee04ff813d2cd0dcc47711f17
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
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.