Files
Ayke van Laethem d4cb92f27c compiler: fix passing weirdly-padded structs to new goroutines
The values were stored in the passed object as the values itself (not
expanded like is common in the calling convention), and read back after
assuming they were expanded. This often works for simple parameters
(int, pointer, etc), but not for more complex parameters. Especially
when there's padding.

Found this while working on `//go:wasmexport`.
2024-09-05 10:53:33 +02:00
..
2024-05-14 20:44:48 +02:00
2023-10-01 18:32:15 +02:00
2023-10-01 18:32:15 +02:00
2024-08-22 07:59:37 +02:00
2021-09-27 15:47:12 +02:00
2023-10-01 18:32:15 +02:00
2023-10-01 18:32:15 +02:00
2023-10-01 18:32:15 +02:00
2024-05-24 19:12:26 +02:00