Speeding up compilation time?

[SolarLune]

Hey, there - I'm compiling to a WASM file through TinyGo, and I notice that compiling through TinyGo is significantly slower than compiling through Go. TinyGo takes 2-3 seconds or so, while Go is almost instantaneous for the same files I have. The output is usable either way, so I know Go isn't producing an empty WASM file, for example.

Any ideas for build options to specify to speed up TinyGo's compilation speed? I have opt=0 already.

[aykevl]

-opt=0 may actually slow down compilation (since it results in a bigger file that needs to be compiled), it is mostly intended for debugging.
Here is an issue that tracks separate compilation, which if implemented will result in a huge speedup since the big LTO step is usually the bottleneck: #2870

[Darckfast]

the WebAssembly GC is mentioned in the LTO issue, did this other issue WebAssembly/gc#59 ever moved forward ?

[aykevl]

The WebAssembly GC would be a lot of work to integrate in TinyGo (probably not impossible, just a lot of work). The main blocker here is that LLVM doesn't have any support for WebAssembly GC (as far as I could see) and we absolutely need that for WebAssembly GC to be viable for TinyGo.

However, there are other ways the GC could be made to work while keeping packages compiling independently.