sago35

after: 5da7119 * linux : 41s * https://app.circleci.com/pipelines/github/tinygo-org/tinygo/3538/workflows/2ba0a518-1161-4572-8eb0-98ab1ec11325/jobs/17680 * macos : 59s * https://app.circleci.com/pipelines/github/tinygo-org/tinygo/3538/workflows/2ba0a518-1161-4572-8eb0-98ab1ec11325/jobs/17675 * windows : 1m42s * https://dev.azure.com/tinygo/tinygo/_build/results?buildId=2070&view=logs&j=ca395085-040a-526b-2ce8-bdc85f692774&t=632617cc-49d1-5f82-37d2-600ea5832b67

The order of the output log is not guaranteed by `make -j`. Also, the lack of the `--output-sync` option on macos makes the log output more difficult to read. However,...

It's not a good idea to write to the same file. I think it needs to be fixed. However, I think #1355 is probably a better way to do it,...

test-llvm11-go116 : make gen-device -j4 * before: * 1m8s * https://app.circleci.com/pipelines/github/tinygo-org/tinygo/4698/workflows/737f4183-f460-4f69-8b69-1f3977c1c815/jobs/26631 * after: * 10s * https://app.circleci.com/pipelines/github/tinygo-org/tinygo/4699/workflows/d54e0a4d-fda8-46a1-ba93-b9f0d75c9493/jobs/26635

Some of the tests failed. Even in my environment, I could not build build/gen-device-svd until I installed libclang-11-dev. build-linux https://app.circleci.com/pipelines/github/tinygo-org/tinygo/4699/workflows/d54e0a4d-fda8-46a1-ba93-b9f0d75c9493/jobs/26639 ``` # Build Tinygo Release #!/bin/bash -eo pipefail make release...

I also think it's a good idea to move it to a different repository.

> moving the generated files over to a separate repository (tinygo.org/device/stm32 etc) which can be used like a regular Go module. How do we put it in `tinygo.org/device/stm32` instead of...

> moving the generated files over to a separate repository (tinygo.org/device/stm32 etc) which can be used like a regular Go module. This idea will make CI faster, so the sooner...

This is not directly related to this PR, but I noticed that the following sources can be unified. I'll discuss it in another PR / Issue. * machine_atsamd51.go * machine_atsame5x.go

> > > This is not directly related to this PR, but I noticed that the following sources can be unified. > I'll discuss it in another PR / Issue....