#![no_main]
#![no_std]
use core::panic::PanicInfo;
use js::*;
mod js {
    #[link(wasm_import_module = "imports")]
    extern "C" {
        pub fn abort(msgPtr: usize, filePtr: usize, line: u32, column: u32) -> !;
        pub fn _log_num(number: usize);
    }
}
#[no_mangle]
pub unsafe extern "C" fn run(worker_id: i32) {
    let worker_index = worker_id as u32 - 1;
    let chunk_start = 100 * worker_index;
    let chunk_end = chunk_start + 100; //Total pixels may not divide evenly into number of worker cores.
    for n in chunk_start as usize..chunk_end as usize {
        _log_num(n);
    }
}
#[panic_handler]
unsafe fn panic(_: &PanicInfo) -> ! { abort(0, 0, 0, 0) }

[target.wasm32-unknown-unknown]
rustflags = [
    "-C", "target-feature=+atomics,+mutable-globals,+bulk-memory",
    "-C", "link-args=--no-entry --shared-memory --import-memory --max-memory=2130706432",
]

const wasmSource = fetch("sim.wasm") //现在开始请求，我们将需要它
//请参阅消息发送代码，了解为什么我们使用多个消息。
let messageArgQueue = [];
addEventListener("message", ({data}) => {
	messageArgQueue.push(data)
	if (messageArgQueue.length === 4) {
		self[messageArgQueue[0]].apply(0, messageArgQueue.slice(1))
	}
})
self.start = async (workerID, worldBackingBuffer, world) => {
	const wasm = await WebAssembly.instantiateStreaming(wasmSource, {
		env: { memory: worldBackingBuffer },
		imports: {
			abort: (messagePtr, locationPtr, row, column) => {
				throw an Error(`? (?:${row}:${column}, thread ${workerID})`)
			},
			_log_num: num => console.log(`thread ${workerID}: n is ${num}`),
		},
	})
	//初始化线程本地存储，以便我们获得独立的堆栈用于我们的局部变量。
	wasm.instance.exports.__wasm_init_tls(workerID-1)	
	//循环，当“tick”前进时运行Rust记录循环。
	let lastProcessedTick = 0
	while (1) {
		Atomics.wait(world.globalTick, 0, lastProcessedTick)
		lastProcessedTick = world.globalTick[0]
		wasm.instance.exports.run(workerID)
	}
}

//让我们数到300。我们将有三个Web Workers，每个负责⅓的任务。0-100, 100-200, 200-300...
//首先，分配一些共享内存。（原始任务想要在各个线程之间共享一些值。）
const memory = new WebAssembly.Memory({
	initial: 23,
	maximum: 23,
	shared: true,
})
//然后，分配到内存的数据视图。
//这是由工作线程更新的共享内存，不在主线程上。
const world = {
	globalTick: new Int32Array(memory.buffer, 1200000, 1), //当前全局tick。增加以告诉工作线程在scratchA中计数！
}
//加载一个核心并将“start”事件发送给它。
const startAWorkerCore = coreIndex => {
	const worker = new Worker('worker/sim.mjs', {type:'module'})
	;['start', coreIndex+1, memory, world].forEach(arg => worker.postMessage(arg)) //由于以下错误，将“start”消息封送到多个postMessage中： 1. 必须在world之前传输内存。 https://bugs.chromium.org/p/ch
<details>
<summary>英文:</summary>
When I run a loop in different Web Workers, the loop shares the counter variable across threads despite that the variable should be thread-local. It should **not** do this, but I don&#39;t know how to fix it.
The offending loop is in the `run` function, as follows in the Rust code being compiled to WASM:
```rust
#![no_main]
#![no_std]
use core::panic::PanicInfo;
use js::*;
mod js {
    #[link(wasm_import_module = &quot;imports&quot;)]
    extern &quot;C&quot; {
        pub fn abort(msgPtr: usize, filePtr: usize, line: u32, column: u32) -&gt; !;
        pub fn _log_num(number: usize);
    }
}
#[no_mangle]
pub unsafe extern &quot;C&quot; fn run(worker_id: i32) {
    let worker_index = worker_id as u32 - 1;
    let chunk_start = 100 * worker_index;
    let chunk_end = chunk_start + 100; //Total pixels may not divide evenly into number of worker cores.
    for n in chunk_start as usize..chunk_end as usize {
        _log_num(n);
    }
}
#[panic_handler]
unsafe fn panic(_: &amp;PanicInfo) -&gt; ! { abort(0, 0, 0, 0) }

[target.wasm32-unknown-unknown]
rustflags = [
    "-C", "target-feature=+atomics,+mutable-globals,+bulk-memory",
    "-C", "link-args=--no-entry --shared-memory --import-memory --max-memory=2130706432",
]

const wasmSource = fetch("sim.wasm") //kick off the request now, we're going to need it
//See message sending code for why we use multiple messages.
let messageArgQueue = [];
addEventListener("message", ({data}) => {
	messageArgQueue.push(data)
	if (messageArgQueue.length === 4) {
		self[messageArgQueue[0]].apply(0, messageArgQueue.slice(1))
	}
})
self.start = async (workerID, worldBackingBuffer, world) => {
	const wasm = await WebAssembly.instantiateStreaming(wasmSource, {
		env: { memory: worldBackingBuffer },
		imports: {
			abort: (messagePtr, locationPtr, row, column) => {
				throw new Error(`? (?:${row}:${column}, thread ${workerID})`)
			},
			_log_num: num => console.log(`thread ${workerID}: n is ${num}`),
		},
	})
	//Initialise thread-local storage, so we get separate stacks for our local variables.
	wasm.instance.exports.__wasm_init_tls(workerID-1)	
	//Loop, running the Rust logging loop when the "tick" advances.
	let lastProcessedTick = 0
	while (1) {
		Atomics.wait(world.globalTick, 0, lastProcessedTick)
		lastProcessedTick = world.globalTick[0]
		wasm.instance.exports.run(workerID)
	}
}

//Let's count to 300. We'll have three web workers, each taking ⅓rd of the task. 0-100, 100-200, 200-300...
//First, allocate some shared memory. (The original task wants to share some values around.)
const memory = new WebAssembly.Memory({
	initial: 23,
	maximum: 23,
	shared: true,
})
//Then, allocate the data views into the memory.
//This is shared memory which will get updated by the worker threads, off the main thread.
const world = {
	globalTick: new Int32Array(memory.buffer, 1200000, 1), //Current global tick. Increment to tell the workers to count up in scratchA!
}
//Load a core and send the "start" event to it.
const startAWorkerCore = coreIndex => {
	const worker = new Worker('worker/sim.mjs', {type:'module'})
	;['start', coreIndex+1, memory, world].forEach(arg => worker.postMessage(arg)) //Marshal the "start" message across multiple postMessages because of the following bugs: 1. Must transfer memory BEFORE world. https://bugs.chromium.org/p/chromium/issues/detail?id=1421524 2. Must transfer world BEFORE memory. https://bugzilla.mozilla.org/show_bug.cgi?id=1821582
}
//Now, let's start some worker threads! They will work on different memory locations, so they don't conflict.
startAWorkerCore(0) //works fine
startAWorkerCore(1) //breaks counting - COMMENT THIS OUT TO FIX COUNTING
startAWorkerCore(2) //breaks counting - COMMENT THIS OUT TO FIX COUNTING
//Run the simulation thrice. Each thread should print a hundred numbers in order, thrice.
//For thread 1, it should print 0, then 1, then 2, etc. up to 99.
//Thread 2 should run from 100 to 199, and thread 3 200 to 299.
//But when they're run simultaneously, all three threads seem to use the same counter.
setTimeout(tick, 500)
setTimeout(tick, 700)
setTimeout(tick, 900)
function tick() {
	Atomics.add(world.globalTick, 0, 1)
	Atomics.notify(world.globalTick, 0)
}