In the runtime package, assembly code can include <code>go_tls.h</code>, which defines
an OS- and architecture-dependent macro <code>get_tls</code> for accessing this register.
The <code>get_tls</code> macro takes one argument, which is the register to load the
<code>g</code> pointer into.
</p>

<p>
For example, the sequence to load <code>g</code> and <code>m</code>

    <_comment>Office Open XML Workbook Add-in (macro-enabled)</_comment>
    <glob pattern="*.xlam"/>
    <sub-class-of type="application/x-tika-ooxml"/>
  </mime-type>

  <mime-type type="application/vnd.ms-excel.sheet.macroenabled.12">
    <_comment>Office Open XML Workbook (macro-enabled)</_comment>
    <glob pattern="*.xlsm"/>
    <sub-class-of type="application/x-tika-ooxml"/>

// * unsigned char is used for booleans (instead of the 'bool' type).
//   In C++ bool is a keyword while in C99 bool is a macro defined
//   in stdbool.h. It is possible for the two to be inconsistent.
//   For example, neither the C99 nor the C++11 standard force a byte
//   size on the bool type, so the macro defined in stdbool.h could
//   be inconsistent with the bool keyword in C++. Thus, the use

pkg debug/macho, const FlagBindsToWeak uint32
pkg debug/macho, const FlagCanonical = 16384
pkg debug/macho, const FlagCanonical uint32
pkg debug/macho, const FlagDeadStrippableDylib = 4194304
pkg debug/macho, const FlagDeadStrippableDylib uint32
pkg debug/macho, const FlagDyldLink = 4
pkg debug/macho, const FlagDyldLink uint32
pkg debug/macho, const FlagForceFlat = 256
pkg debug/macho, const FlagForceFlat uint32

La hiérarchie est la suivante :

* **Uvicorn** : un serveur ASGI
    * **Starlette** : (utilise Uvicorn) un micro-framework web
        * **FastAPI**: (utilise Starlette) un micro-framework pour API disposant de fonctionnalités additionnelles pour la création d'API, avec la validation des données, etc.

* **Uvicorn** :

application/x-troff            t tr roff        # Troff file
application/x-troff-man        man              # Troff with MAN macros
application/x-troff-me         me               # Troff with ME macros
application/x-troff-ms         ms               # Troff with MS macros
application/x-ustar            ustar            # Ustar file
application/vnd.ms-access      mdb mda mde      # MS Access

application/x-troff            t tr roff        # Troff file
application/x-troff-man        man              # Troff with MAN macros
application/x-troff-me         me               # Troff with ME macros
application/x-troff-ms         ms               # Troff with MS macros
application/x-ustar            ustar            # Ustar file
application/vnd.ms-access      mdb mda mde      # MS Access

Lóránt Pintér <******@****.***>
Lóránt Pintér <******@****.***> <******@****.***>
Lóránt Pintér <******@****.***> <******@****.***>
Marcin Erdmann <******@****.***> <******@****.***>
Marco Vermeulen <marco@gradle.com> <******@****.***>
Mark Vieira <******@****.***> <******@****.***>
Michael Barnathan <******@****.***> <******@****.***>
Paul King <******@****.***> <******@****.***>

pkg debug/macho, const CpuArm = 12
pkg debug/macho, const CpuArm Cpu
pkg debug/macho, const CpuPpc = 18
pkg debug/macho, const CpuPpc Cpu
pkg debug/macho, const CpuPpc64 = 16777234
pkg debug/macho, const CpuPpc64 Cpu
pkg debug/macho, const MagicFat = 3405691582
pkg debug/macho, const MagicFat uint32
pkg debug/macho, const TypeBundle = 8
pkg debug/macho, const TypeBundle Type

    /*
     * We use double-checked locking. We could the try racy single-check idiom, but that would
     * depend on Logger to not contain mutable state.
     *
     * We could use Suppliers.memoizingSupplier here, but I micro-optimized to this implementation
     * to avoid the extra class for the lambda (and maybe more for memoizingSupplier itself) and the
     * indirection.
     *