gecko-dev/js/moz.configure

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

638 lines
21 KiB
Plaintext
Raw Normal View History

# -*- Mode: python; indent-tabs-mode: nil; tab-width: 40 -*-
# vim: set filetype=python:
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
# /!\ Use js_option() instead of option() in this file. /!\
# =========================================================
@depends(build_project)
def building_js(build_project):
return build_project == 'js'
# Exception to the rule above: JS_STANDALONE is a special option that doesn't
# want the js_option treatment. When we're done merging js/src/configure and
# top-level configure, it can go away, although the JS_STANDALONE config
# will still need to be set depending on building_js above.
option(env='JS_STANDALONE', default=building_js,
help='Reserved for internal use')
# SmooshMonkey (new frontend)
# ==================================================
# Define here in order to use the option from bindgen.configure.
js_option('--enable-smoosh', default=False,
help='Enable SmooshMonkey (new JS engine frontend)')
@depends('--enable-smoosh')
def enable_smoosh(value):
if value:
return True
set_config('JS_ENABLE_SMOOSH', enable_smoosh)
set_define('JS_ENABLE_SMOOSH', enable_smoosh)
include('../build/moz.configure/rust.configure',
when='--enable-compile-environment')
include('../build/moz.configure/bindgen.configure',
when='--enable-compile-environment')
@depends('JS_STANDALONE')
def js_standalone(value):
if value:
return True
set_config('JS_STANDALONE', js_standalone)
set_define('JS_STANDALONE', js_standalone)
add_old_configure_assignment('JS_STANDALONE', js_standalone)
js_option('--disable-js-shell', default=building_js,
help='{Build|Do not build} the JS shell')
@depends('--disable-js-shell')
def js_disable_shell(value):
if not value:
return True
set_config('JS_DISABLE_SHELL', js_disable_shell)
set_define('JS_64BIT', depends(target)(lambda t: t.bitness == 64 or None))
set_define('JS_PUNBOX64', depends(target)(lambda t: t.bitness == 64 or None))
set_define('JS_NUNBOX32', depends(target)(lambda t: t.bitness == 32 or None))
# SpiderMonkey as a shared library, and how its symbols are exported
# ==================================================================
js_option('--disable-shared-js', when=js_standalone,
help='{Create|Do not create} a shared library')
js_option('--disable-export-js', when=js_standalone,
help='{Mark|Do not mark} JS symbols as DLL exported/visible')
@depends('--disable-shared-js', '--disable-export-js', when=js_standalone)
def shared_js(shared_js, export_js):
if shared_js:
if not export_js:
die('Must export JS symbols when building a shared library.')
return True
set_config('JS_SHARED_LIBRARY', shared_js)
add_old_configure_assignment('JS_SHARED_LIBRARY', shared_js)
@depends(shared_js, '--disable-export-js', when=js_standalone)
def exportable_js_api(shared_js, export_js):
if not shared_js and export_js:
return True
set_define('STATIC_EXPORTABLE_JS_API', exportable_js_api)
@depends(shared_js, exportable_js_api)
def static_js_api(shared_js, export_js):
if not shared_js and not export_js:
return True
set_define('STATIC_JS_API', static_js_api)
@depends(shared_js)
def static_js(value):
if not value:
return True
set_define('MOZ_STATIC_JS', static_js)
js_option(env='NO_RUST_PANIC_HOOK', when=js_standalone,
help='Disable rust panic hook')
set_define('NO_RUST_PANIC_HOOK', True, when='NO_RUST_PANIC_HOOK')
# JIT support
# =======================================================
@depends(target)
def ion_default(target):
if target.cpu in ('x86', 'x86_64', 'arm', 'aarch64', 'mips32', 'mips64'):
return True
return False
js_option('--enable-ion',
default=ion_default,
help='{Enable|Disable} use of the IonMonkey JIT')
# JIT code simulator for cross compiles
# =======================================================
js_option('--enable-simulator', choices=('arm', 'arm64', 'mips32', 'mips64'),
nargs=1,
help='Enable a JIT code simulator for the specified architecture')
@depends('--enable-ion', '--enable-simulator', target)
def simulator(ion_enabled, simulator_enabled, target):
if not ion_enabled or not simulator_enabled:
return
sim_cpu = simulator_enabled[0]
if sim_cpu in ('arm', 'mips32'):
if target.cpu != 'x86':
die('The %s simulator only works on x86.' % sim_cpu)
if sim_cpu in ('arm64', 'mips64'):
if target.cpu != 'x86_64':
die('The %s simulator only works on x86-64.' % sim_cpu)
return namespace(**{sim_cpu: True})
set_config('JS_SIMULATOR', depends_if(simulator)(lambda x: True))
set_config('JS_SIMULATOR_ARM', simulator.arm)
set_config('JS_SIMULATOR_ARM64', simulator.arm64)
set_config('JS_SIMULATOR_MIPS32', simulator.mips32)
set_config('JS_SIMULATOR_MIPS64', simulator.mips64)
set_define('JS_SIMULATOR', depends_if(simulator)(lambda x: True))
set_define('JS_SIMULATOR_ARM', simulator.arm)
set_define('JS_SIMULATOR_ARM64', simulator.arm64)
set_define('JS_SIMULATOR_MIPS32', simulator.mips32)
set_define('JS_SIMULATOR_MIPS64', simulator.mips64)
@depends('--enable-ion', simulator, target)
def jit_codegen(ion_enabled, simulator, target):
if not ion_enabled:
return namespace(none=True)
if simulator:
return simulator
if target.cpu == 'aarch64':
return namespace(arm64=True)
elif target.cpu == 'x86_64':
return namespace(x64=True)
return namespace(**{str(target.cpu): True})
set_config('JS_CODEGEN_NONE', jit_codegen.none)
set_config('JS_CODEGEN_ARM', jit_codegen.arm)
set_config('JS_CODEGEN_ARM64', jit_codegen.arm64)
set_config('JS_CODEGEN_MIPS32', jit_codegen.mips32)
set_config('JS_CODEGEN_MIPS64', jit_codegen.mips64)
set_config('JS_CODEGEN_X86', jit_codegen.x86)
set_config('JS_CODEGEN_X64', jit_codegen.x64)
set_define('JS_CODEGEN_NONE', jit_codegen.none)
set_define('JS_CODEGEN_ARM', jit_codegen.arm)
set_define('JS_CODEGEN_ARM64', jit_codegen.arm64)
set_define('JS_CODEGEN_MIPS32', jit_codegen.mips32)
set_define('JS_CODEGEN_MIPS64', jit_codegen.mips64)
set_define('JS_CODEGEN_X86', jit_codegen.x86)
set_define('JS_CODEGEN_X64', jit_codegen.x64)
# Profiling
# =======================================================
js_option('--enable-instruments', env='MOZ_INSTRUMENTS',
help='Enable instruments remote profiling')
@depends('--enable-instruments', target)
def instruments(value, target):
if value and target.os != 'OSX':
die('--enable-instruments cannot be used when targeting %s',
target.os)
if value:
return True
set_config('MOZ_INSTRUMENTS', instruments)
set_define('MOZ_INSTRUMENTS', instruments)
add_old_configure_assignment('MOZ_INSTRUMENTS', instruments)
imply_option('--enable-profiling', instruments, reason='--enable-instruments')
js_option('--enable-callgrind', env='MOZ_CALLGRIND',
help='Enable callgrind profiling')
@depends('--enable-callgrind')
def callgrind(value):
if value:
return True
set_define('MOZ_CALLGRIND', callgrind)
imply_option('--enable-profiling', callgrind)
@depends(milestone)
def enable_profiling(milestone):
return milestone.is_nightly
js_option('--enable-profiling', env='MOZ_PROFILING', default=enable_profiling,
help='{Set|Do not set} compile flags necessary for using sampling '
'profilers (e.g. shark, perf)')
@depends('--enable-profiling')
def profiling(value):
if value:
return True
add_old_configure_assignment('MOZ_PROFILING', profiling)
with only_when('--enable-compile-environment'):
imply_option('--enable-frame-pointers', True, when=profiling)
@depends(profiling, target)
def imply_vtune(value, target):
ok_cpu = target.cpu in ['x86', 'x86_64']
ok_kernel = target.kernel == 'WINNT' or \
(target.kernel == 'Linux' and target.os == 'GNU')
if value and ok_cpu and ok_kernel:
return True
set_config('MOZ_PROFILING', profiling)
set_define('MOZ_PROFILING', profiling)
imply_option('--enable-vtune', imply_vtune, reason='--enable-profiling')
js_option('--enable-vtune', env='MOZ_VTUNE', help='Enable VTune profiling')
@depends('--enable-vtune')
def vtune(value):
if value:
return True
set_config('MOZ_VTUNE', vtune)
set_define('MOZ_VTUNE', vtune)
js_option('--enable-gc-trace', env='JS_GC_TRACE',
help='Enable tracing of allocation and finalization')
@depends('--enable-gc-trace')
def gc_trace(value):
if value:
return True
set_define('JS_GC_TRACE', gc_trace)
js_option('--enable-gczeal',
default=depends(when=moz_debug)(lambda: True),
help='{Enable|Disable} zealous GCing')
set_define('JS_GC_ZEAL',
depends_if('--enable-gczeal')(lambda _: True))
# Use a smaller chunk size for GC chunks
# ========================================================
# Use large (1MB) chunks by default. This option can be used to give
# smaller (currently 256K) chunks.
js_option('--enable-small-chunk-size',
help='Allocate memory for JS GC things in smaller chunks')
set_define('JS_GC_SMALL_CHUNK_SIZE',
depends(when='--enable-small-chunk-size')(lambda: True))
# Trace logging.
# =======================================================
@depends(milestone)
def default_trace_logging(milestone):
return milestone.is_nightly
js_option('--enable-trace-logging',
default=default_trace_logging,
help='{Enable|Disable} trace logging')
set_config('ENABLE_TRACE_LOGGING',
depends_if('--enable-trace-logging')(lambda x: True))
set_define('JS_TRACE_LOGGING',
depends_if('--enable-trace-logging')(lambda x: True))
# Enable breakpoint for artificial OOMs
# =======================================================
js_option('--enable-oom-breakpoint',
help='Enable a breakpoint function for artificial OOMs')
set_define('JS_OOM_BREAKPOINT',
depends_if('--enable-oom-breakpoint')(lambda _: True))
js_option('--enable-perf', env='JS_ION_PERF',
help='Enable Linux perf integration')
@depends('--enable-perf')
def ion_perf(value):
if value:
return True
set_define('JS_ION_PERF', ion_perf)
js_option('--enable-jitspew',
default=depends(when=moz_debug)(lambda: True),
help='{Enable|Disable} the Jit spew and IONFLAGS environment '
'variable')
set_define('JS_JITSPEW',
depends_if('--enable-jitspew')(lambda _: True))
set_config('JS_JITSPEW',
depends_if('--enable-jitspew')(lambda _: True))
# Also enable the structured spewer
set_define('JS_STRUCTURED_SPEW',
depends_if('--enable-jitspew')(lambda _: True))
set_config('JS_STRUCTURED_SPEW',
depends_if('--enable-jitspew')(lambda _: True))
@depends('--enable-ion', '--enable-jitspew', simulator, target, moz_debug)
def jit_disasm_arm(ion_enabled, spew, simulator, target, debug):
if not ion_enabled:
return
if simulator and (debug or spew):
if getattr(simulator, 'arm', None):
return True
if target.cpu == 'arm' and (debug or spew):
return True
set_config('JS_DISASM_ARM', jit_disasm_arm)
set_define('JS_DISASM_ARM', jit_disasm_arm)
@depends('--enable-ion', '--enable-jitspew', simulator, target, moz_debug)
def jit_disasm_arm64(ion_enabled, spew, simulator, target, debug):
if not ion_enabled:
return
if simulator and (debug or spew):
if getattr(simulator, 'arm64', None):
return True
if target.cpu == 'aarch64' and (debug or spew):
return True
set_config('JS_DISASM_ARM64', jit_disasm_arm64)
set_define('JS_DISASM_ARM64', jit_disasm_arm64)
# When enabled, masm will generate assumeUnreachable calls that act as
# assertions in the generated code. This option is worth disabling when you
# have to track mutated values through the generated code, to avoid constantly
# dumping registers on and off the stack.
js_option('--enable-masm-verbose',
default=depends(when=moz_debug)(lambda: True),
help='{Enable|Disable} MacroAssembler verbosity of generated code.')
set_define('JS_MASM_VERBOSE',
depends_if('--enable-masm-verbose')(lambda _: True))
set_config('JS_MASM_VERBOSE',
depends_if('--enable-masm-verbose')(lambda _: True))
js_option('--enable-more-deterministic', env='JS_MORE_DETERMINISTIC',
help='Enable changes that make the shell more deterministic')
@depends('--enable-more-deterministic')
def more_deterministic(value):
if value:
return True
set_define('JS_MORE_DETERMINISTIC', more_deterministic)
# CTypes
# =======================================================
@depends(building_js)
def ctypes_default(building_js):
return not building_js
js_option('--enable-ctypes',
default=ctypes_default,
help='{Enable|Disable} js-ctypes')
build_ctypes = depends_if('--enable-ctypes')(lambda _: True)
set_config('BUILD_CTYPES', build_ctypes)
set_define('BUILD_CTYPES', build_ctypes)
@depends(build_ctypes, building_js)
def js_has_ctypes(ctypes, js):
if ctypes and js:
return True
set_config('JS_HAS_CTYPES', js_has_ctypes)
set_define('JS_HAS_CTYPES', js_has_ctypes)
@depends('--enable-ctypes', '--enable-compile-environment')
def ctypes_and_compile_environment(ctypes, compile_environment):
return ctypes and compile_environment
include('ffi.configure', when=ctypes_and_compile_environment)
# Enable pipeline operator
# ===================================================
js_option('--enable-pipeline-operator', default=False, help='Enable pipeline operator')
@depends('--enable-pipeline-operator')
def enable_pipeline_operator(value):
if value:
return True
set_config('ENABLE_PIPELINE_OPERATOR', enable_pipeline_operator)
set_define('ENABLE_PIPELINE_OPERATOR', enable_pipeline_operator)
# Experimental support for BinAST
# ==============================================================
@depends(milestone.is_nightly)
def default_binast(is_nightly):
return is_nightly
js_option('--enable-binast',
default=default_binast,
help="{Enable|Disable} BinAST support")
set_config('JS_BUILD_BINAST', depends_if('--enable-binast')(lambda x: True))
set_define('JS_BUILD_BINAST', depends_if('--enable-binast')(lambda x: True))
# SIMD acceleration for encoding_rs
# ==============================================================
js_option('--enable-rust-simd', env='MOZ_RUST_SIMD',
help='Enable explicit SIMD in Rust code.')
@depends('--enable-rust-simd', target)
def rust_simd(value, target):
# As of 2019-09-17, the simd-accel feature of encoding_rs has not
# been properly set up outside aarch64, armv7, x86 and x86_64.
if target.cpu in ('aarch64', 'arm', 'x86', 'x86_64') and value:
return True
set_config('MOZ_RUST_SIMD', rust_simd)
set_define('MOZ_RUST_SIMD', rust_simd)
# Experimental support for wasm code generation with Cranelift
Bug 1566427 - Improved compiler availability computation. r=bbouvier This patch cleans up wasm compiler selection and a few related things with as few semantic changes as possible. The intent is to centralize compiler availability computation so that all parts of the system stay in sync and it is easy to change compiler selection policy. First, we introduce new predicates <Compiler>Available(cx) to test for the actual availability of a compiler. These predicates take into account whether a compiler is compiled into the executable, whether it supports the hardware, whether it is (currently) selected by options/switches, and whether it can be used as a result of the runtime environment (for example, Ion and Cranelift are not available if the debugger is observing the page or if the GC feature is enabled; Cranelift is not available if shared memory and atomics are enabled). We switch to using these predicates almost everywhere that used <Compiler>CanCompile() or cx->options().wasm<Compiler>(), since those don't tell the full story. Second, we implement a priority order of the optimizing compilers and make it easy to change this order (see comments in code). At the moment, Cranelift is prioritized over Ion since Ion is enabled by default and Cranelift is not; thus the desire of somebody flipping the pref for Cranelift is to deselect Ion. The priority order may change in the future or may become platform-dependent. The default compiler selection in both browser and shell remains Baseline+Ion. Third, we rename HasCompilerSupport() as HasPlatformSupport(), since the predicate does not test whether compilers are available, only whether they are present in the executable and support the hardware. And to make that more sensible, <Compiler>CanCompile() is renamed as <Compiler>PlatformSupport(). Fourth, we remove some redundant testing predicates (we don't need both wasmDebugSupport and wasmDebuggingIsSupported, nor do we need wasmUsesCranelift because wasmCompileMode is more reliable). Fifth, we introduce a few new test cases that try to ensure that compiler selection works as it should. These are white-box and may need to change if the compiler priority order changes. Sixth, we rename the internal wasm::Has<Feature>Support() predicates as wasm::<Feature>Available(), since they all actually test for compiler availability. Differential Revision: https://phabricator.services.mozilla.com/D64946 --HG-- extra : moz-landing-system : lando
2020-03-11 15:03:45 +00:00
#
# Note, you may have to disable features not supported by Cranelift
# (multi-value, threads) to make Cranelift actually available
# ==============================================================
js_option('--enable-cranelift',
default=milestone.is_nightly,
help='{Enable|Disable} Cranelift code generator for wasm')
set_config('ENABLE_WASM_CRANELIFT', depends_if('--enable-cranelift')(lambda x: True))
set_define('ENABLE_WASM_CRANELIFT', depends_if('--enable-cranelift')(lambda x: True))
# Support for debugging code generated by wasm backends
# =====================================================
js_option('--enable-wasm-codegen-debug',
default=depends(when=moz_debug)(lambda: True),
help='{Enable|Disable} debugging for wasm codegen')
set_config('WASM_CODEGEN_DEBUG', depends_if('--enable-wasm-codegen-debug')(lambda x: True))
set_define('WASM_CODEGEN_DEBUG', depends_if('--enable-wasm-codegen-debug')(lambda x: True))
# Support for typed objects.
# =====================================================
@depends(milestone.is_nightly)
def default_typed_objects(is_nightly):
return is_nightly
js_option('--enable-typed-objects',
default=default_typed_objects,
help='{Enable|Disable} typed objects')
set_config('JS_HAS_TYPED_OBJECTS', depends_if('--enable-typed-objects')(lambda x: True))
set_define('JS_HAS_TYPED_OBJECTS', depends_if('--enable-typed-objects')(lambda x: True))
# Support for WebAssembly bulk memory operations.
# =====================================================
@depends(milestone.is_nightly)
def default_wasm_bulk_memory(is_nightly):
return is_nightly
js_option('--enable-wasm-bulk-memory',
default=default_wasm_bulk_memory,
help='{Enable|Disable} WebAssembly bulk memory operators')
set_config('ENABLE_WASM_BULKMEM_OPS', depends_if('--enable-wasm-bulk-memory')(lambda x: True))
set_define('ENABLE_WASM_BULKMEM_OPS', depends_if('--enable-wasm-bulk-memory')(lambda x: True))
# Support for WebAssembly reference types.
# =====================================================
@depends(milestone.is_nightly)
def default_wasm_reftypes(is_nightly):
return is_nightly
js_option('--enable-wasm-reftypes',
default=default_wasm_reftypes,
help='{Enable|Disable} WebAssembly reference types')
set_config('ENABLE_WASM_REFTYPES', depends_if('--enable-wasm-reftypes')(lambda x: True))
set_define('ENABLE_WASM_REFTYPES', depends_if('--enable-wasm-reftypes')(lambda x: True))
# Support for WebAssembly I64/BigInt conversion
# ===========================================================================
@depends(milestone.is_nightly)
def default_wasm_bigint(is_nightly):
return is_nightly
js_option('--enable-wasm-bigint',
default=default_wasm_bigint,
help='{Enable|Disable} WebAssembly I64/BigInt conversion')
set_config('ENABLE_WASM_BIGINT', depends_if('--enable-wasm-bigint')(lambda x: True))
set_define('ENABLE_WASM_BIGINT', depends_if('--enable-wasm-bigint')(lambda x: True))
# Support for WebAssembly GC.
# ===========================
@depends(milestone.is_nightly, '--enable-wasm-reftypes')
def default_wasm_gc(is_nightly, reftypes):
if reftypes and is_nightly:
return True
js_option('--enable-wasm-gc',
default=default_wasm_gc,
help='{Enable|Disable} WebAssembly GC')
set_config('ENABLE_WASM_GC', depends_if('--enable-wasm-gc')(lambda x: True))
set_define('ENABLE_WASM_GC', depends_if('--enable-wasm-gc')(lambda x: True))
# Support for WebAssembly private ref types.
# Prevent (ref T) types from being exposed to JS content so that wasm need do
# no typechecking at the JS/wasm boundary
# ===========================================================================
@depends(milestone.is_nightly, '--enable-wasm-gc')
def default_wasm_private_reftypes(is_nightly, gc):
if gc and is_nightly:
return True
js_option('--enable-wasm-private-reftypes',
default=default_wasm_private_reftypes,
help='{Enable|Disable} WebAssembly private reference types')
set_config('WASM_PRIVATE_REFTYPES', depends_if('--enable-wasm-private-reftypes')(lambda x: True))
set_define('WASM_PRIVATE_REFTYPES', depends_if('--enable-wasm-private-reftypes')(lambda x: True))
# Support for the WebAssembly multi-value proposal.
Bug 1566427 - Improved compiler availability computation. r=bbouvier This patch cleans up wasm compiler selection and a few related things with as few semantic changes as possible. The intent is to centralize compiler availability computation so that all parts of the system stay in sync and it is easy to change compiler selection policy. First, we introduce new predicates <Compiler>Available(cx) to test for the actual availability of a compiler. These predicates take into account whether a compiler is compiled into the executable, whether it supports the hardware, whether it is (currently) selected by options/switches, and whether it can be used as a result of the runtime environment (for example, Ion and Cranelift are not available if the debugger is observing the page or if the GC feature is enabled; Cranelift is not available if shared memory and atomics are enabled). We switch to using these predicates almost everywhere that used <Compiler>CanCompile() or cx->options().wasm<Compiler>(), since those don't tell the full story. Second, we implement a priority order of the optimizing compilers and make it easy to change this order (see comments in code). At the moment, Cranelift is prioritized over Ion since Ion is enabled by default and Cranelift is not; thus the desire of somebody flipping the pref for Cranelift is to deselect Ion. The priority order may change in the future or may become platform-dependent. The default compiler selection in both browser and shell remains Baseline+Ion. Third, we rename HasCompilerSupport() as HasPlatformSupport(), since the predicate does not test whether compilers are available, only whether they are present in the executable and support the hardware. And to make that more sensible, <Compiler>CanCompile() is renamed as <Compiler>PlatformSupport(). Fourth, we remove some redundant testing predicates (we don't need both wasmDebugSupport and wasmDebuggingIsSupported, nor do we need wasmUsesCranelift because wasmCompileMode is more reliable). Fifth, we introduce a few new test cases that try to ensure that compiler selection works as it should. These are white-box and may need to change if the compiler priority order changes. Sixth, we rename the internal wasm::Has<Feature>Support() predicates as wasm::<Feature>Available(), since they all actually test for compiler availability. Differential Revision: https://phabricator.services.mozilla.com/D64946 --HG-- extra : moz-landing-system : lando
2020-03-11 15:03:45 +00:00
# Do not remove until Cranelift supports multi-value.
# =====================================================
@depends(milestone.is_nightly)
def default_wasm_multi_value(is_nightly):
return is_nightly
js_option('--enable-wasm-multi-value',
default=default_wasm_multi_value,
help='{Enable|Disable} support for the experimental WebAssembly '
'multi-value proposal')
set_config('ENABLE_WASM_MULTI_VALUE', depends_if('--enable-wasm-multi-value')(lambda x: True))
set_define('ENABLE_WASM_MULTI_VALUE', depends_if('--enable-wasm-multi-value')(lambda x: True))
Bug 1566427 - Improved compiler availability computation. r=bbouvier This patch cleans up wasm compiler selection and a few related things with as few semantic changes as possible. The intent is to centralize compiler availability computation so that all parts of the system stay in sync and it is easy to change compiler selection policy. First, we introduce new predicates <Compiler>Available(cx) to test for the actual availability of a compiler. These predicates take into account whether a compiler is compiled into the executable, whether it supports the hardware, whether it is (currently) selected by options/switches, and whether it can be used as a result of the runtime environment (for example, Ion and Cranelift are not available if the debugger is observing the page or if the GC feature is enabled; Cranelift is not available if shared memory and atomics are enabled). We switch to using these predicates almost everywhere that used <Compiler>CanCompile() or cx->options().wasm<Compiler>(), since those don't tell the full story. Second, we implement a priority order of the optimizing compilers and make it easy to change this order (see comments in code). At the moment, Cranelift is prioritized over Ion since Ion is enabled by default and Cranelift is not; thus the desire of somebody flipping the pref for Cranelift is to deselect Ion. The priority order may change in the future or may become platform-dependent. The default compiler selection in both browser and shell remains Baseline+Ion. Third, we rename HasCompilerSupport() as HasPlatformSupport(), since the predicate does not test whether compilers are available, only whether they are present in the executable and support the hardware. And to make that more sensible, <Compiler>CanCompile() is renamed as <Compiler>PlatformSupport(). Fourth, we remove some redundant testing predicates (we don't need both wasmDebugSupport and wasmDebuggingIsSupported, nor do we need wasmUsesCranelift because wasmCompileMode is more reliable). Fifth, we introduce a few new test cases that try to ensure that compiler selection works as it should. These are white-box and may need to change if the compiler priority order changes. Sixth, we rename the internal wasm::Has<Feature>Support() predicates as wasm::<Feature>Available(), since they all actually test for compiler availability. Differential Revision: https://phabricator.services.mozilla.com/D64946 --HG-- extra : moz-landing-system : lando
2020-03-11 15:03:45 +00:00
# Support for WebAssembly shared memory and atomics.
#
# This affects the JS shell only and here to allow the use of
# Cranelift in the shell. Once Cranelift supports shared memory
# and atomics it can go away.
# =====================================================
js_option('--disable-shared-memory', help='Disable JS/WebAssembly shared memory and atomics')
Bug 1566427 - Improved compiler availability computation. r=bbouvier This patch cleans up wasm compiler selection and a few related things with as few semantic changes as possible. The intent is to centralize compiler availability computation so that all parts of the system stay in sync and it is easy to change compiler selection policy. First, we introduce new predicates <Compiler>Available(cx) to test for the actual availability of a compiler. These predicates take into account whether a compiler is compiled into the executable, whether it supports the hardware, whether it is (currently) selected by options/switches, and whether it can be used as a result of the runtime environment (for example, Ion and Cranelift are not available if the debugger is observing the page or if the GC feature is enabled; Cranelift is not available if shared memory and atomics are enabled). We switch to using these predicates almost everywhere that used <Compiler>CanCompile() or cx->options().wasm<Compiler>(), since those don't tell the full story. Second, we implement a priority order of the optimizing compilers and make it easy to change this order (see comments in code). At the moment, Cranelift is prioritized over Ion since Ion is enabled by default and Cranelift is not; thus the desire of somebody flipping the pref for Cranelift is to deselect Ion. The priority order may change in the future or may become platform-dependent. The default compiler selection in both browser and shell remains Baseline+Ion. Third, we rename HasCompilerSupport() as HasPlatformSupport(), since the predicate does not test whether compilers are available, only whether they are present in the executable and support the hardware. And to make that more sensible, <Compiler>CanCompile() is renamed as <Compiler>PlatformSupport(). Fourth, we remove some redundant testing predicates (we don't need both wasmDebugSupport and wasmDebuggingIsSupported, nor do we need wasmUsesCranelift because wasmCompileMode is more reliable). Fifth, we introduce a few new test cases that try to ensure that compiler selection works as it should. These are white-box and may need to change if the compiler priority order changes. Sixth, we rename the internal wasm::Has<Feature>Support() predicates as wasm::<Feature>Available(), since they all actually test for compiler availability. Differential Revision: https://phabricator.services.mozilla.com/D64946 --HG-- extra : moz-landing-system : lando
2020-03-11 15:03:45 +00:00
@depends('--disable-shared-memory')
def enable_shared_memory(value):
if value:
return True
Bug 1566427 - Improved compiler availability computation. r=bbouvier This patch cleans up wasm compiler selection and a few related things with as few semantic changes as possible. The intent is to centralize compiler availability computation so that all parts of the system stay in sync and it is easy to change compiler selection policy. First, we introduce new predicates <Compiler>Available(cx) to test for the actual availability of a compiler. These predicates take into account whether a compiler is compiled into the executable, whether it supports the hardware, whether it is (currently) selected by options/switches, and whether it can be used as a result of the runtime environment (for example, Ion and Cranelift are not available if the debugger is observing the page or if the GC feature is enabled; Cranelift is not available if shared memory and atomics are enabled). We switch to using these predicates almost everywhere that used <Compiler>CanCompile() or cx->options().wasm<Compiler>(), since those don't tell the full story. Second, we implement a priority order of the optimizing compilers and make it easy to change this order (see comments in code). At the moment, Cranelift is prioritized over Ion since Ion is enabled by default and Cranelift is not; thus the desire of somebody flipping the pref for Cranelift is to deselect Ion. The priority order may change in the future or may become platform-dependent. The default compiler selection in both browser and shell remains Baseline+Ion. Third, we rename HasCompilerSupport() as HasPlatformSupport(), since the predicate does not test whether compilers are available, only whether they are present in the executable and support the hardware. And to make that more sensible, <Compiler>CanCompile() is renamed as <Compiler>PlatformSupport(). Fourth, we remove some redundant testing predicates (we don't need both wasmDebugSupport and wasmDebuggingIsSupported, nor do we need wasmUsesCranelift because wasmCompileMode is more reliable). Fifth, we introduce a few new test cases that try to ensure that compiler selection works as it should. These are white-box and may need to change if the compiler priority order changes. Sixth, we rename the internal wasm::Has<Feature>Support() predicates as wasm::<Feature>Available(), since they all actually test for compiler availability. Differential Revision: https://phabricator.services.mozilla.com/D64946 --HG-- extra : moz-landing-system : lando
2020-03-11 15:03:45 +00:00
set_config('ENABLE_SHARED_MEMORY', enable_shared_memory)
set_define('ENABLE_SHARED_MEMORY', enable_shared_memory)
Bug 1566427 - Improved compiler availability computation. r=bbouvier This patch cleans up wasm compiler selection and a few related things with as few semantic changes as possible. The intent is to centralize compiler availability computation so that all parts of the system stay in sync and it is easy to change compiler selection policy. First, we introduce new predicates <Compiler>Available(cx) to test for the actual availability of a compiler. These predicates take into account whether a compiler is compiled into the executable, whether it supports the hardware, whether it is (currently) selected by options/switches, and whether it can be used as a result of the runtime environment (for example, Ion and Cranelift are not available if the debugger is observing the page or if the GC feature is enabled; Cranelift is not available if shared memory and atomics are enabled). We switch to using these predicates almost everywhere that used <Compiler>CanCompile() or cx->options().wasm<Compiler>(), since those don't tell the full story. Second, we implement a priority order of the optimizing compilers and make it easy to change this order (see comments in code). At the moment, Cranelift is prioritized over Ion since Ion is enabled by default and Cranelift is not; thus the desire of somebody flipping the pref for Cranelift is to deselect Ion. The priority order may change in the future or may become platform-dependent. The default compiler selection in both browser and shell remains Baseline+Ion. Third, we rename HasCompilerSupport() as HasPlatformSupport(), since the predicate does not test whether compilers are available, only whether they are present in the executable and support the hardware. And to make that more sensible, <Compiler>CanCompile() is renamed as <Compiler>PlatformSupport(). Fourth, we remove some redundant testing predicates (we don't need both wasmDebugSupport and wasmDebuggingIsSupported, nor do we need wasmUsesCranelift because wasmCompileMode is more reliable). Fifth, we introduce a few new test cases that try to ensure that compiler selection works as it should. These are white-box and may need to change if the compiler priority order changes. Sixth, we rename the internal wasm::Has<Feature>Support() predicates as wasm::<Feature>Available(), since they all actually test for compiler availability. Differential Revision: https://phabricator.services.mozilla.com/D64946 --HG-- extra : moz-landing-system : lando
2020-03-11 15:03:45 +00:00
# Initial support for new regexp engine
# ==================================================
js_option('--enable-new-regexp', default=False, help='Enable new regexp engine')
@depends('--enable-new-regexp')
def enable_new_regexp(value):
if value:
return True
set_config('ENABLE_NEW_REGEXP', enable_new_regexp)
set_define('ENABLE_NEW_REGEXP', enable_new_regexp)