Add more testing for pthread_kill.

- Test using `pthread_kill` on yourself.
- Test using `pthread_kill` from a background thread to the main thread.
4 files changed
tree: 1ebab10e39dffea8d121d535a06666bab184dc18
  1. .circleci/
  2. .github/
  3. cmake/
  4. docs/
  5. html/
  6. media/
  7. site/
  8. src/
  9. system/
  10. test/
  11. third_party/
  12. tools/
  13. .clang-format
  14. .clang-format-ignore
  15. .editorconfig
  16. .git-blame-ignore-revs
  17. .gitattributes
  18. .gitignore
  19. .gitmodules
  20. .prettierrc.yml
  21. .style.yapf
  22. AUTHORS
  23. bootstrap
  24. bootstrap.bat
  25. bootstrap.py
  26. ChangeLog.md
  27. CONTRIBUTING.md
  28. em++.py
  29. em-config.py
  30. emar.py
  31. embuilder.py
  32. emcc.py
  33. emcmake.py
  34. emconfigure.py
  35. emmake.py
  36. emranlib.py
  37. emrun.py
  38. emscan-deps.py
  39. emscons.py
  40. emscripten-version.txt
  41. emsize.py
  42. emstrip.py
  43. eslint.config.mjs
  44. LICENSE
  45. Makefile
  46. package-lock.json
  47. package.json
  48. pyproject.toml
  49. README.md
  50. requirements-dev.txt
  51. SECURITY.md
README.md

emscripten logo

Main project page: https://emscripten.org

GitHub CI status: CircleCI

Chromium builder status: emscripten-releases

Overview

Emscripten compiles C and C++ to WebAssembly using LLVM and Binaryen. Emscripten output can run on the Web, in Node.js, and in wasm runtimes.

Emscripten provides Web support for popular portable APIs such as OpenGL and SDL2, allowing complex graphical native applications to be ported, such as the Unity game engine and Google Earth. It can probably port your codebase, too!

While Emscripten mostly focuses on compiling C and C++ using Clang, it can be integrated with other LLVM-using compilers (for example, Rust has Emscripten integration, with the wasm32-unknown-emscripten target).

License

Emscripten is available under 2 licenses, the MIT license and the University of Illinois/NCSA Open Source License.

Both are permissive open source licenses, with little if any practical difference between them.

The reason for offering both is that (1) the MIT license is well-known and suitable for a compiler toolchain, while (2) LLVM‘s original license, the University of Illinois/NCSA Open Source License, was also offered to allow Emscripten’s code to be integrated upstream into LLVM. The second reason became less important after Emscripten switched to the LLVM wasm backend, at which point there isn't any code we expect to move back and forth between the projects; also, LLVM relicensed to Apache 2.0 + exceptions meanwhile. In practice you can just consider Emscripten as MIT licensed (which allows you to do pretty much anything you want with a compiler, including commercial and non-commercial use).

See LICENSE for the full content of the licenses.