Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Conflicts:
src/parseTools.js
src/preamble.js
|
|
test suite
|
|
|
|
|
|
Conflicts:
src/parseTools.js
|
|
no_copy_vfs_to_heap
|
|
footprint and fread() performance over the default behavior that copied VFS to HEAP, that is designed for mmap() performance.
Adjust MEMFS node contentMode enum to reflect whether content is off the main HEAP or not. Note that this enum is not much used, so this has little effect. Add browser tests to check that fread() and mmap() work with and without --no-heap-copy.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
support, and rename option to PRECISE_F32 to be consistent with other precision options
|
|
|
|
|
|
The issue is that when these macros are defined, libcxx
creates inline functions and so we end up with 2 separate
defintions of these functions (one inline in std and one
that is extern "C").
We undef these until libcxx is fixed. Without this,
some things can fail to compile correctly, like
Boost. Fixes issue #1716.
|
|
|
|
|
|
|
|
requires running in administrative mode. (Also atm fails on a few node.js-specific crossplatform discrepancies)
|
|
|
|
a problem
|
|
|
|
|
|
|
|
initializer
|
|
|
|
|
|
|
|
|
|
generated functions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
chars and char codes.
|
|
|
|
|
|
|
|
|