| HEAD | 78b286e | Update test_no_legalize_js_ffi in preparation for binaryen change (#21599) See https://github.com/WebAssembly/binaryen/pull/6428 | 23 March 2024, 00:27:09 UTC |
| refs/heads/11880-test | 54e4307 | Merge remote-tracking branch 'origin/master' into 11880-test | 12 August 2020, 22:17:48 UTC |
| refs/heads/EM_FROZEN_CACHE | d5951d2 | Fix handling of EM_FROZEN_CACHE=0. NFC | 17 August 2022, 23:40:50 UTC |
| refs/heads/abort_on_preload_failure | d7592f8 | Abort of preload failure It seems better to fail early in the this case than try to continue in some half preloaded state. | 10 March 2023, 23:36:22 UTC |
| refs/heads/add_lit_tests | 593a480 | WIP: Experiment with using lit as a test runner | 26 July 2021, 21:45:15 UTC |
| refs/heads/add_main_module_test | 8c86080 | Re-enable metadce main module test This was disabled back #9120 because it was deemed to fragile. This change re-enables it but using a C program rathe than a C++ one so it doesn't include the C++ standard library which makes it way smaller and without a gazillion obscure exports. Also switch to use `self.build` to compile these tests so that we get the C vs C++ handling that exists here. Tracking the symbol list used during a minimal MAIN_MODULE=1 build is useful for my upcoming PIC ABI changes to see the effect it has. | 07 October 2020, 18:46:42 UTC |
| refs/heads/allow_import_minification | 8bcc002 | Fix DECLARE_ASM_MODULE_EXPORTS so it doesn't prevent import minifiction This option is designed only to prevent export minification only. | 04 March 2023, 00:45:59 UTC |
| refs/heads/already | 5d7d8ff | work | 15 May 2023, 19:51:03 UTC |
| refs/heads/android.wasm | f62196f | fixens [ci skip] | 18 October 2023, 21:16:18 UTC |
| refs/heads/appending_settings | 61d5ed6 | Allow certain command line settings to be additive For certain command line settings (specifically most settings that take a list) it is useful to be able to add to the existing setting rather than replace it. For example, the `-sEXPORTED_FUNCTIONS` argument. In a build system where different components can inject link flags it makes sense that each component be able add to the list of exported functions without clobbering the current list. We have had this feature requested several times in the past. For example, from the bazel toolchain folks. | 31 July 2023, 18:21:24 UTC |
| refs/heads/async-funcs-arent-asyncify | 5647eb4 | Don't mark proxy async funcs as Asyncify In #19093 both async functions and functions marked with `NAME__async: true` were marked as functions to be processed by Asyncify. However, looking at usages, standalone async functions are currently used with emscripten_proxy_finish-based callbacks and not with Asyncify. Besides, such functions can't work with Asyncify unless we add automatic `Asyncify.handleAsync` wrapping around each such function as well. We could do that, but given that there are already is some confusion around what async means for any particular function, it seems better to keep explicit calls to `emscripten_proxy_finish` and `Asyncify.handleAsync` correspondingly. Hence, in this PR I'm not adding more automatic wrapping but instead just removing the assumption for standalone async functions which should somewhat reduce code size as they will no longer be Asyncify-ed when not necessary. | 12 September 2023, 00:26:48 UTC |
| refs/heads/async3 | ae20233 | more [ci skip] | 09 September 2020, 21:14:41 UTC |
| refs/heads/async_pthread_shutdown | ba07983 | Attempt to terminate workers cooperatively This change is designed fix address pthread thread flakiness around process termination. For example see #19683 and #15014. In some cases I believe that workers are being terminated while they have postMessage messages in their queue, so messages are getting lost. In other cases we are seeing message arrive after the call to `terminate()`. This change attempts to avoid using `terminate()` at all and attempts to cooperatively shut down the worker. We only use `terminate()` if the thread doesn't respond in a certain amount of time. | 28 June 2023, 18:02:51 UTC |
| refs/heads/atobie | 34cf9ef | move comment | 15 November 2021, 21:20:45 UTC |
| refs/heads/autodebug | 6e81315 | simpler | 12 November 2020, 22:31:53 UTC |
| refs/heads/avoid_debugging | 81d5e3c | Avoid excessive console logging in browser tests. NFC This was resulting a lot of noise in console logs which get recorded by CI which meant circle CI was always saying: ``` Your output is too large to display in the browser. Only the last 400000 characters are displayed. ``` | 21 June 2021, 23:56:27 UTC |
| refs/heads/avoid_delete | 34b02e6 | Avoid using JS `delete` for array elements. NFC See https://github.com/emscripten-core/emscripten/pull/19054#discussion_r1146928736 | 01 May 2023, 19:29:16 UTC |
| refs/heads/avoid_exports | 68771c3 | Only export user-requests symbols on the Module object. NFC Some exports are only needed internally and those don't need to be exported on the Module object. This is save some space and avoids unexpected exports on the public-facing Module. | 07 July 2022, 03:32:07 UTC |
| refs/heads/browser_report_stdout_stderr | 47e6608 | browser_reporting.js: report stderr and stdout back to server This means that anything send to stdout or stderr during browser testing is reports back to server which is especially useful in headless testing which is used in our CI. | 25 August 2021, 17:53:06 UTC |
| refs/heads/ccall | db53e59 | fix test | 31 January 2019, 22:01:15 UTC |
| refs/heads/change_default_log_level | eb403ef | Change default log level to WARN to avoid spamming stderr By default we don't want random messages such as `cache:INFO: generating system asset:` from appearing on stdout. EMCC_DEBUG and EMCC_VERBOSE can be used enable more info. Fixes: #18622, #18607 | 28 March 2023, 00:09:31 UTC |
| refs/heads/clang-format | 07772ba | Add clang-format to github actions I would have prefered to use an actual pre-packaged github action for this. There seem to be very many of these but none of them seems to have the most important feature here which is the ability to run just on the diff and not on the entire repo. This probably shouldn't land until we figure out exactly what parts of the tree we want to run this on. I'm thinking probably `tests` but also any part of `system` that are emscripten-local. We also might want to do a quick first pass at formatting these things before landing this. | 06 October 2020, 15:40:55 UTC |
| refs/heads/cleanup_browser_reporting | 2a24b91 | Unify `onerror` handler used by test framework | 10 August 2021, 17:39:18 UTC |
| refs/heads/cleanup_memory_init | 9c63bb7 | Minor cleanup of runtime_init_memory.js - Only update INITIAL_MEMORY if we recieved a memory from the user. - Unconditionally set buffer to wasmMemory.buffer | 05 November 2020, 00:05:22 UTC |
| refs/heads/cleanup_test_chunked_synchronous_xhr | bda5848 | Cleanup test_chunked_synchronous_xhr. NFC | 27 May 2022, 21:57:16 UTC |
| refs/heads/closure.fs | bf08dab | fix | 21 December 2022, 00:13:17 UTC |
| refs/heads/closure.quoted | ddcae42 | yolo | 11 October 2023, 17:30:32 UTC |
| refs/heads/codecov | 3cdfc38 | [WIP] Add codecov support | 07 August 2023, 18:17:23 UTC |
| refs/heads/cored8 | ac26557 | Add `corev8` test suite that runs all core tests under v8/d8. NFC | 23 February 2023, 22:38:35 UTC |
| refs/heads/crt1_everywhere | f154139 | Use _emscripten_start rather than _main as program entry point. Now, applications will always get linked with crt1.o (or some flavor of it) which exports the `_emscripten_start` function. This function take care of calling the users main function as well as running static constructor. | 10 June 2022, 00:16:20 UTC |
| refs/heads/default_global_base | 15255eb | Only pass --global-base to the linker if its set to a non-default value Otherwise rely on the linker default value of 1024. This change is in preparation of using `--stack-first` in debug builds. When `--stack-first` is passed to the linker `--global-base` is ignored (it should really be an error do this). I also avoid needless passing redundant arguments to the linker. | 13 October 2022, 19:04:40 UTC |
| refs/heads/dependabot/github_actions/actions/checkout-4.1.2 | 54b6066 | Bump actions/checkout from 4.1.0 to 4.1.2 Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.0 to 4.1.2. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/8ade135a41bc03ea155e62e844d188df1ea18608...9bb56186c3b09b4f86b1c65136769dd318469633) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> | 18 March 2024, 22:20:03 UTC |
| refs/heads/dependabot/github_actions/actions/upload-artifact-4.3.1 | 2f49530 | Bump actions/upload-artifact from 3.1.2 to 4.3.1 Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.1.2 to 4.3.1. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](https://github.com/actions/upload-artifact/compare/0b7f8abb1508181956e8e162db84b466c27e18ce...5d5d22a31266ced268874388b861e4b58bb5c2f3) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> | 05 February 2024, 22:16:27 UTC |
| refs/heads/dependabot/github_actions/github/codeql-action-3.24.8 | 36caad1 | Bump github/codeql-action from 3.23.1 to 3.24.8 Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.23.1 to 3.24.8. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/0b21cf2492b6b02c465a3e5d7c473717ad7721ba...05963f47d870e2cb19a537396c1f668a348c7d8f) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> | 18 March 2024, 22:19:56 UTC |
| refs/heads/dependabot/github_actions/ossf/scorecard-action-2.3.1 | 8d4dc1f | Bump ossf/scorecard-action from 2.1.3 to 2.3.1 Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.1.3 to 2.3.1. - [Release notes](https://github.com/ossf/scorecard-action/releases) - [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md) - [Commits](https://github.com/ossf/scorecard-action/compare/80e868c13c90f172d68d1f4501dee99e2479f7af...0864cf19026789058feabb7e87baa5f140aac736) --- updated-dependencies: - dependency-name: ossf/scorecard-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> | 23 October 2023, 22:58:29 UTC |
| refs/heads/distinguish_stdout_and_logging | fd03b3d | Distinguish between stdout and stderr and emscripten logging (out and err) It can be useful to be able to tell the difference between emscripten's internal log message (calls to err() and out()) and the actual program stderr and stdout. As an example here I attach the thread ID to all emscripten log message when running with USE_PTHREADS. | 05 March 2021, 03:10:51 UTC |
| refs/heads/dylink_weakly_defined_symbols | 46f0777 | . | 18 August 2021, 21:39:13 UTC |
| refs/heads/early_abort | 2fa958e | Move some code in shell.js to allow abort() to be called early on. NFC Split out from #18845 | 24 February 2023, 21:01:36 UTC |
| refs/heads/em_js_export | 10fa18d | Use `__attribute__(export_name)` over `EMSCRIPTEN_KEEPALIVE` in `EM_JS` macro The `EMSCRIPTEN_KEEPALIVE` macro relies on `attribute((used))` which works slightly differently under emscripten (`wasm32-unknown-emscripten`) compared to other triples. This change avoids `EMSCRIPTEN_KEEPALIVE` here in favor of the `export_name` attribute which is more precise and correct although not (yet) suitable for us in `EMSCRIPTEN_KEEPALIVE` itself (We would need something like https://reviews.llvm.org/D76547 to make that work). | 29 January 2022, 19:39:03 UTC |
| refs/heads/emval-reftypes | 879d855 | Fix WireType | 01 October 2023, 23:18:50 UTC |
| refs/heads/environment_checks | 17f31f2 | Guard `ENVIRONMENT_IS_SHELL` check This matches the pattern used for ENVIRONMENT_IS_SHELL and ENVIRONMENT_IS_WEB elsewhere in this file. Fixes: #18411 | 21 December 2022, 16:17:33 UTC |
| refs/heads/es_version_settings | 81090f5 | Add control over JS version used in input and output of emscripten T6his allows users more control of the version of JS they want to produce and the version they want to use in their input. It also fixes a bug where were introducing non-ES5 features into our output files by using closer with --language_out set to NO_TRANSPILE and --language_in set to ECMASCRIPT_2020. Fixes: #12628 | 28 October 2020, 18:19:33 UTC |
| refs/heads/excdoc | 82b5c1b | typo | 01 March 2022, 18:25:47 UTC |
| refs/heads/executable_output | cef98c8 | Make output scripts executable by default when targeting node This is something we already did autoconf mode. | 27 February 2023, 23:26:54 UTC |
| refs/heads/exitJS_proxy | 339d3ae | Proxy exitJS synchronously, just like the low level proc_exit This simplifies the code and reduces code size. Add testing of both `exit` and `_exit` in test_pthread_exit_runtime. | 16 February 2023, 18:14:45 UTC |
| refs/heads/export | d774118 | add EMSCRIPTEN_EXPORT option | 25 February 2017, 00:09:27 UTC |
| refs/heads/export_name | 3d67c4e | Error on EXPORT_NAME without MODULARIZE. NFC One doesn't make sense without that other. Fixes: #17274 | 20 June 2022, 16:12:14 UTC |
| refs/heads/fcoverage | 2aa40c7 | Add initial support -fcoverage-mapping support This is enought make it work up until llvm-cov tries to read the named data sections in the binary and can't find them. For this final part to work we probably need to switch the object format to using multiple code and data sections: https://github.com/WebAssembly/tool-conventions/issues/138 Not sure if its worth submitting this part in isolation without a fully working solution? See #13046 | 17 December 2020, 11:43:41 UTC |
| refs/heads/feat.env | bfb6f5b | fix | 17 April 2023, 23:21:03 UTC |
| refs/heads/feedback | 768ca7b | Feedback from #19239. NFC | 25 April 2023, 00:13:15 UTC |
| refs/heads/fetch_handle_alloc | d2ad502 | Use HandleAllocator for fetch API. NFC | 11 May 2023, 18:25:50 UTC |
| refs/heads/fetch_timeout2 | 02a1fb7 | Set fetch status to 408 on timeout This allows the caller of the API to detect the timeout occurred. Fixes: #18658 | 08 February 2023, 00:32:59 UTC |
| refs/heads/file_packager | 998d002 | file_packager.py: Use last occurrence of @ in --preload-file This means that `@@` escaping is optional for the targets rather than the source. Fixes #15947 | 11 January 2022, 23:31:51 UTC |
| refs/heads/fix-features-docs | 3ef9878 | various updates | 22 November 2022, 22:00:26 UTC |
| refs/heads/fix_8678 | f1edf5a | wip [ci skip] | 12 July 2019, 19:12:43 UTC |
| refs/heads/fix_benchmarker | 9d8c26d | Fix Benchmarker JS utility. NFC | 05 December 2022, 22:47:28 UTC |
| refs/heads/fix_deadlock | 2179619 | Fix deadlock when calling fflush during application shutdown One solution to the deadlock described in #15186 is to allow nested calls to `emscripten_current_thread_process_queued_calls`. This is needed in this case because the main thread is calling `fflush` (which requires locking the stdout handle) while another thread is holding the stdout lock, waiting on the main thread to process the write action. There may be reasons we don't want to allow nested calls to `emscripten_current_thread_process_queued_calls` but technically its seems possible. This change removes all the mitigations that existed in `test_pthread_c11_threads.c` and I could no longer reprodude the deadlock. Fixes: #15186 | 30 September 2021, 18:49:46 UTC |
| refs/heads/fix_internal_setting_name | a2f78a6 | Rename internal MINIFY_ASMJS_EXPORT_NAMES setting. NFC | 11 October 2022, 14:38:16 UTC |
| refs/heads/fix_noderawfs | 5631f48 | Fix NODERAWFS regression caused by #19391 Thanks to @kleisauke for pointing out that the old code always passed -1 as the second argument and not `nfd`. `nfd` here is the node raw FD which is different the FD space we return to the user. | 02 June 2023, 21:29:04 UTC |
| refs/heads/fix_st_ino_truncated | d5bff30 | Truncate inode number when writing to st_ino_truncated. NFC This field is designed to hold a potentially truncated inode number, as opposes the st_ino which hold the full 64-bit value. Fixes: #19567 | 08 June 2023, 22:05:36 UTC |
| refs/heads/force_filesystem_exports | 3bfd463 | Limit exports generated by FORCE_FILEYSTEM Specifically, only export symbols that are actually neede by the output of the file packager. | 12 June 2023, 18:39:06 UTC |
| refs/heads/fpic_relocatable | 7c923ad | Set RELOCATABLE if `-fPIC` is passed on the command line Also avoid adding `-fPIC` a second time if it already exists. This is a partial fix for #14488 since now building with `-fPIC -s USE_LIBJPEG=1` will correctly cause the `pic` version of libjpeg to be built and installed. This is hard to test for since it involves something that is mostly and internal detail (which verion of libjpeg is build when copiling with `-c`). I decided to instead test for another side effect of `-s RELOCATABLE` which is the `-fvisibility=default` compiler flag. | 19 June 2021, 02:30:04 UTC |
| refs/heads/fs_handle_alloc | 8118082 | Use HandleAllocator in legacy FS. NFC | 18 May 2023, 01:18:41 UTC |
| refs/heads/fuzz-exceptions | 023d93f | updates [ci skip] | 27 February 2021, 01:42:34 UTC |
| refs/heads/gl.shift.4gb | a9a7bb0 | add disabled test | 12 September 2022, 20:13:51 UTC |
| refs/heads/gl_handle_alloc | b6f5cc4 | Use HandleAllocator for GL object. NFC | 28 February 2023, 19:02:35 UTC |
| refs/heads/glfw_use_elif | 4b956cf | Use #elif directive in src/library_glfw.js. NFC | 13 March 2022, 04:51:49 UTC |
| refs/heads/handledByPreloadPlugin | 3cabc20 | yolo | 20 December 2022, 20:30:58 UTC |
| refs/heads/implement_some_wasi2 | e6ccdf7 | Implement a few more WASI APIs Followup to #12704. | 01 April 2023, 00:47:01 UTC |
| refs/heads/inline_doDup | 32b0f58 | Inline doDup into its only remaining caller. NFC Noticed in comments on #14808 | 22 March 2022, 23:46:48 UTC |
| refs/heads/js_optimizer_nested_object | d74db16 | Fix parsing of nested object patterns in acorn-optimizer.js Fixes: #20818 | 04 December 2023, 20:50:09 UTC |
| refs/heads/lazy | 745cc3c | fix [ci skip] | 29 November 2020, 00:40:19 UTC |
| refs/heads/leb128_from_pip | 95431ed | Use pip to install leb128 python module Rather than checking in our python dependencies we can now use pip to install them. This is our first usage of pip to installing packages outside of test code. This means that from now on git users will be expected to run `pip install -r requirements` (with or without the `--target .pip` is fine. For emsdk users will will want to run `pip install` either and emsdk install time or at emsdk build time (like we do with npm). Once this mechanism is in place we will be free to use whatever pip packages we choose in emscripten's codebase. See: https://github.com/emscripten-core/emsdk/pull/1001 | 21 March 2022, 17:07:32 UTC |
| refs/heads/libcxxabi-debug | e4d6ef7 | Add debug build of libc++-abi There is code in libc++-abi that contains asserts so being able to build it is debug mode has some value. | 29 March 2022, 21:22:24 UTC |
| refs/heads/limit_export_name | e4d5e60 | Limit the use of EXPORT_NAME to when MODULARIZE is set EXPORT_NAME doesn't make any sense without MODULARIZE. | 15 January 2023, 15:22:08 UTC |
| refs/heads/linux_arm | 5c53a73 | [CI] Add some testing of linux/arm64. NFC | 06 September 2023, 16:54:02 UTC |
| refs/heads/local_sysroot | dfbfa50 | Add support for "local" subdirectory of sysroot Automatically add `sysroot/local/include` and `sysroot/local/lib` to the include and library path. Also, use this new local subdirectory by default in emscripten by passing `--prefix=<sysroot>/local`. This should make `emconfigure + make install` work out of the box. Also, add `sysroot/lib` to the library path which allows libraries installed via `./configure --prefix=<sysroot>` and then `make install` to be found automativally. Fixes: #13753 | 25 March 2021, 02:31:51 UTC |
| refs/heads/log.audio | 9157c8f | Add a changelog note about Audio Worklets [NFC] | 10 February 2023, 18:10:41 UTC |
| refs/heads/main | 78b286e | Update test_no_legalize_js_ffi in preparation for binaryen change (#21599) See https://github.com/WebAssembly/binaryen/pull/6428 | 23 March 2024, 00:27:09 UTC |
| refs/heads/main_module_no_pic | 951654f | Stop building main modules as relocatable Fixes #12682 | 02 November 2020, 19:40:47 UTC |
| refs/heads/main_module_static | 6308498 | Avoid using RELOCATABLE by default when building with MAIN_MODULE By building main module as non-relocatable we can improve the code size and performance of the main module. There is no good reason to build the main module as relocatable, only the side module really need this. One downside is that this reduces our coverage of the `RELOCATABLE` option to just a few isolated test cases. I wonder if we should consider removing this option unless there are other compelling use cases? This change depends and llvm-side change: https://reviews.llvm.org/D91577 | 19 January 2022, 22:18:14 UTC |
| refs/heads/malloc_debug | ff5f466 | Remove DLMALLOC_DEBUG and abort() override dlmalloc already has `DEBUG` macros that is used to enable debugging, so just use that one for consistency. In terms replacing abort with direct call to __builtin_unreachable this seems a little odd to do that here but not in other places. `abort` is a call to an import so is also a single instruction, and the JS version of abort has almost no chance of being completely avoided (even the smallest program will likely reference it). Perhaps this comment dates back to a different time when abort was implemented differently or perhaps it refers to the difference is size between a `call` instruction and a `trap` instruction in the binary. However, the ABORT macro is mostly only used in the `DEBUG` version of dlmalloc so this argument doesn't make much sense. See #15662 and #15628 | 24 November 2021, 18:59:43 UTC |
| refs/heads/memset_big | 7cfd1be | Add emscripten_memset_big based on HEAPU8.fill() Improves benchmark.test_memset_1mb from 500ms to 170ms. This should help with #18628. | 01 April 2023, 16:30:15 UTC |
| refs/heads/move_code_into_library_js | c31277f | Migrate pre/postable code in library.js | 29 June 2023, 16:46:52 UTC |
| refs/heads/nested_user_callback | f830b53 | Detect nested usage of callUserCallback. NFC Detect cases where `callUserCallback` is called while already running user code. This doesn't change the behaviour, but warns about (currently) incorrect usage of `callUserCallback`. Split out from #17441 which fixes a real bug in glfw where `callUserCallback` could cause the runtime to exit mid-program. This bug only effects programs that are built with `EXIT_RUNTIME` but its serious enough we probably want to look at more robust solution. For now, issuing a warning seems like a good first step. | 19 July 2022, 17:45:33 UTC |
| refs/heads/node_env | 4d54914 | Mirror entire environment under node One can still use `-sDETERMINISITIC` to avoid this behaviour. Fixes: #18816 | 22 February 2023, 16:12:51 UTC |
| refs/heads/node_warnOnce | adeff39 | Highlight `warnOnce` warnings under node (#17477) On the web we don't need do this since console.warn are already shown as warnings. However, under node its nice if the warnings stand out from other stuff being written to stderr. | 20 July 2022, 04:27:05 UTC |
| refs/heads/nofin | b39ba89 | cleanup | 31 January 2021, 19:53:12 UTC |
| refs/heads/old_incoming | eecf6f5 | Hide stderr when running llmv-nm --print-armap (#10198) The stderr contains "no symbols" for each input object that doesn't have any symbols at all. Fixes: #10191 | 14 January 2020, 00:27:38 UTC |
| refs/heads/partunmap | 8b14ebd | fix condition | 23 June 2021, 23:41:23 UTC |
| refs/heads/pdoc | 494b4e6 | feedback | 10 November 2020, 17:42:54 UTC |
| refs/heads/profiling_funcs | 7edaf47 | [tes] Include name section (--profiling-funcs) in non-optimized builds These means a lot more tests will show useful backtraces. Fixes: #15470 | 11 November 2021, 23:52:50 UTC |
| refs/heads/pthread | 958055b | Rename PThreadinitMainThreadBlock => PThread.prepareMainThread for clarity | 26 October 2020, 16:26:38 UTC |
| refs/heads/pthread_abort | 0aafb2e | Add (failing) test for abort() from pthread. NFC Currently disabled because we have an outstanding but that abort() does not work in threads: #11345 | 26 November 2020, 03:26:22 UTC |
| refs/heads/pthreads_dynamic_linking | fc4ccc3 | Initial support for pthreads + dynamic linking See #3494 | 10 November 2020, 20:53:23 UTC |
| refs/heads/python_typing_part3 | 58b509f | Adding python types, part 3. NFC This change enabled `disallow_untyped_defs` which forces all functions to be typed, but initially only for `tools/shared.py`. This process uncovered a typo in the exception path of `get_clang_targets`. | 21 September 2022, 11:14:36 UTC |
| refs/heads/reenable | d18a98d | Re-enable test_pthread_create_standalone Assuming updating node took care of the flakiness, this will fix #18405 | 01 June 2023, 20:39:13 UTC |
| refs/heads/refactor_pthread_entry_part2 | 10ab94a | Move more code out of worker.js Followup to #17087. | 28 May 2022, 17:52:15 UTC |
| refs/heads/reftest_simplify | ccaaec2 | tests: Avoid duplicating/inlining browser_reporting.js within reftest.js This file was duplicated/inlined into reftest.js for the case where the module is running on worker (e.g. proxy-to-worker) and therefore the copy that gets included via `--pre-js` is not accessible However, we can simplify this by simply directly including `browser_reporting.js` when we use it in this way. | 17 July 2022, 02:59:41 UTC |
| refs/heads/remove_asmCoercion | a7e6159 | Remove asmCoercion familiy of functions from parseTools.js. NFC These don't have a role to play any longer in a non-asm.js world. | 11 June 2021, 17:39:52 UTC |
