Lines Matching refs:pexe

10 bitcode (a ``.pexe`` file), using as much architecture-neutral optimization as
11 possible.  The ``.pexe`` file is downloaded to the user's browser where the
12 PNaCl translator (a component of Chrome) compiles the ``.pexe`` file to
33   speed, or the ``.pexe`` file is already cached while the translated binary was
55 | Parse .pexe file                       | Parse .pexe file            |
92 We'd like to be able to translate a ``.pexe`` file as fast as download speed.
97 ``.pexe`` file could be compressed to 50% on the web server using gzip transport
116 developer environment.  The ``.pexe`` file reflects these optimizations.  For
136 some of LLVM's bitcode decoding code (for binary-format ``.pexe`` files), again
147 ``.pexe`` files can lead to the translator process holding hundreds of MB of
157 total ``.pexe`` file size.  Simply put, Subzero should not have memory leaks or
167 internally splits a ``.pexe`` file into several modules for concurrent
201 IR, which is reflected in the ``.pexe`` file's bitcode structure.  It has a
207 The ``.pexe`` file is translated one function at a time (or in parallel by
369 Subzero includes an integrated PNaCl bitcode parser for ``.pexe`` files.  It
370 parses the ``.pexe`` file function by function, ultimately constructing an ICE
385 - Parse the next function from the ``.pexe`` file and construct a CFG consisting
423   label names that are present in the ``.pexe`` file.  This would allow a
424   debugger to map addresses back to symbols in the ``.pexe`` file.
426 - To map ``.pexe`` file symbols back to meaningful source-level symbol names,
431 - The PNaCl toolchain explicitly strips all this from the ``.pexe`` file, and so
1045 - A single thread parses the ``.pexe`` file and produces a sequence of work
1114 If there is a popular ``.pexe`` with a large install base, the attacker could
1122 opposed to mischief from a malicious ``.pexe`` file.
1308 We have started fuzz-testing the ``.pexe`` files input to Subzero, using a
1347 linking to the ``.pexe`` file specifies the ``O0`` optimization level.
1495 translation speed.  For a large ``.pexe`` file, the time breaks down as:
1539 on the size of functions in the ``.pexe`` file.
1542 ``pnacl-llc.pexe``, which is the largest ``.pexe`` file (7.2 MB) at our