You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Emterpreter has largerly been replaces by asyncify and is fastcomp only
so due for removing in the near future anyway.
The reason I'm pulling this forward ahead of fastcomp deprecation
is that it unblocks some other refactoring I'm working on.
exit_with_error('cannot have both WASM=2 and SINGLE_FILE enabled at the same time (pick either JS to target with -s WASM=0 or Wasm to target with -s WASM=1)')
1227
1221
@@ -1459,19 +1453,6 @@ def has_c_source(args):
1459
1453
ifnotshared.Settings.WASM_BACKEND:
1460
1454
exit_with_error('ASYNCIFY has been removed from fastcomp. There is a new implementation which can be used in the upstream wasm backend.')
1461
1455
1462
-
ifshared.Settings.EMTERPRETIFY:
1463
-
diagnostics.warning('emterpreter', 'emterpreter is soon to be removed. If you depend on this feature please reach out on github for help transitioning.')
1464
-
shared.Settings.FINALIZE_ASM_JS=0
1465
-
shared.Settings.SIMPLIFY_IFS=0# this is just harmful for emterpreting
exit_with_error('EMTERPRETIFY requires valid asm.js, and is incompatible with closure 2 which disables that')
1473
-
assertnotuse_source_map(options), 'EMTERPRETIFY is not compatible with source maps (maps are not useful in emterpreted code, and splitting out non-emterpreted source maps is not yet implemented)'
exit_with_error("DISABLE_EXCEPTION_THROWING was set (probably from -fno-exceptions) but is not compatible with enabling exception catching (DISABLE_EXCEPTION_CATCHING=0). If you don't want exceptions, set DISABLE_EXCEPTION_CATCHING to 1; if you do want exceptions, don't link with -fno-exceptions")
exit_with_error('-s SIDE_MODULE=1 is not supported with -s USE_PTHREADS>0!')
1636
1617
ifshared.Settings.MAIN_MODULE:
1637
1618
exit_with_error('-s MAIN_MODULE=1 is not supported with -s USE_PTHREADS>0!')
1638
-
ifshared.Settings.EMTERPRETIFY:
1639
-
exit_with_error('-s EMTERPRETIFY=1 is not supported with -s USE_PTHREADS>0!')
1640
1619
ifshared.Settings.PROXY_TO_WORKER:
1641
1620
exit_with_error('--proxy-to-worker is not supported with -s USE_PTHREADS>0! Use the option -s PROXY_TO_PTHREAD=1 if you want to run the main thread of a multithreaded application in a web worker.')
# we cannot have an EM_ASM on the stack when saving/loading
1010
-
pre_asm_const+=" assert(typeof EmterpreterAsync !== 'object' || EmterpreterAsync.state !== 2, 'cannot have an EM_ASM on the stack when emterpreter pauses/resumes - the JS is not emterpreted, so we would end up running it again from the start');\n"
1011
-
1012
1002
asm_const_funcs.append(r'''
1013
1003
function _emscripten_asm_const_%s(%s) {
1014
1004
%s return ASM_CONSTS[code](%s);
@@ -1352,7 +1342,7 @@ def closure(other):
1352
1342
defasm_backend_uses(metadata, symbol):
1353
1343
# If doing dynamic linking, we should generate full set of runtime primitives, since we cannot know up front ahead
1354
1344
# of time what the dynamically linked in modules will need. Also with SAFE_HEAP and Emterpretify, generate full set of views.
Copy file name to clipboardExpand all lines: site/source/docs/api_reference/emscripten.h.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1039,7 +1039,7 @@ Functions
1039
1039
Returns whether pseudo-synchronous functions can be used.
1040
1040
1041
1041
:rtype: int
1042
-
:returns: 1 if program was compiled with ASYNCIFY=1 or EMTERPRETER_ASYNC=1, 0 otherwise.
1042
+
:returns: 1 if program was compiled with ASYNCIFY=1, 0 otherwise.
1043
1043
1044
1044
1045
1045
.. c:function:: void emscripten_debugger()
@@ -1252,7 +1252,7 @@ Typedefs
1252
1252
Pseudo-synchronous functions
1253
1253
============================
1254
1254
1255
-
These functions require Asyncify (``-s ASYNCIFY=1``) with the wasm backend, or Emterpreter-async with fastcomp (``-s EMTERPRETIFY=1 -s EMTERPRETIFY_ASYNC=1``). These functions are asynchronous but appear synchronous in C. See `Asyncify <https://emscripten.org/docs/porting/asyncify.html>`_ and `Emterpreter <https://emscripten.org/docs/porting/emterpreter.html>`_ for more details.
1255
+
These functions require Asyncify (``-s ASYNCIFY=1``). These functions are asynchronous but appear synchronous in C. See `Asyncify <https://emscripten.org/docs/porting/asyncify.html>`_ for more details.
Copy file name to clipboardExpand all lines: site/source/docs/api_reference/preamble.js.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ Calling compiled C functions from JavaScript
70
70
:returns: The result of the function call as a native JavaScript value (as in ``returnType``) or, if the ``async`` option is set, a JavaScript Promise of the result.
71
71
:opts: An optional options object. It can contain the following properties:
72
72
73
-
- ``async``: If ``true``, implies that the ccall will perform an async operation. This assumes you are using the Emterpreter-Async option for your code.
73
+
- ``async``: If ``true``, implies that the ccall will perform an async operation. This assumes you are build with asyncify support.
74
74
75
75
.. note:: Async calls currently don't support promise error handling.
Copy file name to clipboardExpand all lines: site/source/docs/optimizing/Optimizing-Code.rst
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,6 @@ In addition to the above, the following tips can help to reduce code size:
80
80
- Use :ref:`the closure compiler <emcc-closure>` on the non-compiled code: ``--closure 1``. This can hugely reduce the size of the support JavaScript code, and is highly recommended. However, if you add your own additional JavaScript code (in a ``--pre-js``, for example) then you need to make sure it uses `closure annotations properly <https://developers.google.com/closure/compiler/docs/api-tutorial3>`_.
81
81
- `Floh's blogpost on this topic <http://floooh.github.io/2016/08/27/asmjs-diet.html>`_ is very helpful.
82
82
- Make sure to use gzip compression on your webserver, which all browsers now support.
83
-
- You can move some of your code into the `Emterpreter <https://github.com/emscripten-core/emscripten/wiki/Emterpreter>`_, which will then run much slower (as it is interpreted), but it will transfer all that code into a smaller amount of data.
84
83
85
84
The following compiler settings can help (see ``src/settings.js`` for more details):
0 commit comments