Emscripten may or may not support threads, based on whether or not the right compiler flags are given:

This compiles without threads by default:

emcc -o mps.o -c code/mps.c

But this will have threads:

emcc -s USE_PTHREADS=1 -o mps.o -c code/mps.c

I don't want to use a separate target entirely for threads vs not-threads, so I only have a single block in code/mps.c to include the right files, and I can build with it including lockix.c.

lockix.c will fall back to not supporting threads if CONFIG_THREAD_SINGLE is defined, which changes things so that LOCK is not defined and LOCK_NONE is. In that case, it switches to the lockan.c implementation automatically.

Is this an acceptable use / abuse of CONFIG_THREAD_SINGLE?

#elif defined(__EMSCRIPTEN__) && defined(__wasm32__)
#if defined(CONFIG_PF_STRING) && ! defined(CONFIG_PF_EMJ3LL)
#error "specified CONFIG_PF_... inconsistent with detected emj3ll"
#endif
#define MPS_PF_EMJ3LL
#define MPS_PF_STRING   "emj3ll"
#define MPS_OS_EM
#define MPS_ARCH_J3
#define MPS_BUILD_LL
#define MPS_T_WORD      unsigned long
#define MPS_T_ULONGEST  unsigned long
#define MPS_WORD_WIDTH  32
#define MPS_WORD_SHIFT  5
#define MPS_PF_ALIGN    4

#if !defined(__EMSCRIPTEN_PTHREADS__)
#define CONFIG_THREAD_SINGLE
#endif

MPS does not support WebAssembly #168

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions