Skip to content

Commit 44170ce

Browse files
authored
Remove is_wasm_only() which only made sense on fastcomp (#12067)
1 parent e5df8fc commit 44170ce

File tree

2 files changed

+0
-11
lines changed

2 files changed

+0
-11
lines changed

emcc.py

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1780,9 +1780,6 @@ def include_and_export(name):
17801780
if shared.Settings.USE_PTHREADS:
17811781
newargs.append('-pthread')
17821782

1783-
if not shared.Settings.LEGALIZE_JS_FFI:
1784-
assert building.is_wasm_only(), 'LEGALIZE_JS_FFI incompatible with RUNNING_JS_OPTS.'
1785-
17861783
# check if we can address the 2GB mark and higher: either if we start at
17871784
# 2GB, or if we allow growth to either any amount or to 2GB or more.
17881785
if shared.Settings.INITIAL_MEMORY > 2 * 1024 * 1024 * 1024 or \

tools/building.py

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -856,14 +856,6 @@ def can_inline():
856856
return Settings.INLINING_LIMIT == 0
857857

858858

859-
def is_wasm_only():
860-
# not even wasm, much less wasm-only
861-
if not Settings.WASM:
862-
return False
863-
# llvm backend can only ever produce wasm
864-
return True
865-
866-
867859
def get_safe_internalize():
868860
if Settings.LINKABLE:
869861
return [] # do not internalize anything

0 commit comments

Comments
 (0)