Tinygo - Go-компилятор для встраиваемых систем (форк https://github.com/tinygo-org/tinygo) С поддержкой сборки динамических библиотек
Найти файл
Adrian Cole 334a12818d Allows the emulator to expand {tmpDir}
This allows you to expand {tmpDir} in the json "emulator" field, and
uses it in wasmtime instead of custom TMPDIR mapping logic.

Before, we had custom logic for wasmtime to create a separate tmpDir
when running go tests. This overwrite the TMPDIR variable when running,
after making a mount point. A simpler way to accomplish the end goal of
writing temp files is to use wasmtime's map-dir instead. When code is
compiled to wasm with the wasi target, tempDir is always /tmp, so we
don't need to add variables (since we know what it is). Further, the
test code is the same between normal go and run through wasmtime. So, we
don't need to make a separate temp dir first, and avoiding that reduces
logic, as well makes it easier to swap out the emulator (for wazero
which has no depedencies). To map the correct directory, this introduces
a {tmpDir} token whose value is the host-specific value taken from
`os.TempDir()`.

The motivation I have for this isn't so much to clean up the wasmtime
code, but allow wazero to execute the same tests. After this change, the
only thing needed to pass tests is to change the emulator, due to
differences in how wazero deals with relative lookups (they aren't
restricted by default, so there's not a huge amount of custom logic
needed).

In other words, installing wazero from main, `make tinygo-test-wasi`
works with no other changes except this PR and patching
`targets/wasi.json`.
```json
	"emulator":      "wazero run -mount=.:/ -mount={tmpDir}:/tmp {}",
```

On that note, if there's a way to override the emulator via arg or env,
this would be even better, but in any case patching json is fine.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
2023-01-19 20:06:18 +01:00
.circleci builder: add support for Go 1.20 2023-01-17 08:38:54 +01:00
.github/workflows build: update docker GH action to use latest docker action versions 2022-11-21 10:59:59 +01:00
bin all: add stub pieces for GoLand support 2018-12-01 18:32:34 +01:00
builder all: remove remaining +build lines 2023-01-17 23:35:53 +01:00
cgo builder: add support for Go 1.20 2023-01-17 08:38:54 +01:00
compileopts Allows the emulator to expand {tmpDir} 2023-01-19 20:06:18 +01:00
compiler compiler,runtime: make keySize and valueSize uintptr 2023-01-18 09:48:00 +01:00
docs docs: change links in README and remove old ReadTheDocs pages to point to TinyGo.org site 2019-01-13 20:29:45 +01:00
goenv goenv: update to new v0.27.0 development version 2022-10-13 12:06:48 +02:00
hooks dockerhub: use post checkout hook for git submodule init 2020-08-03 08:30:31 +02:00
interp runtime: implement precise GC 2023-01-17 19:32:18 +01:00
lib Revert "Bump CMSIS to 5.9.0" 2022-12-16 21:26:49 +01:00
loader cgo: implement support for static functions 2022-09-16 14:05:17 +02:00
src compiler,runtime: make keySize and valueSize uintptr 2023-01-18 09:48:00 +01:00
stacksize build: support machine outlining pass in stacksize calculation 2022-03-12 12:55:38 +01:00
targets Allows the emulator to expand {tmpDir} 2023-01-19 20:06:18 +01:00
testdata builder: add support for Go 1.20 2023-01-17 08:38:54 +01:00
tests build: drop deprecated build tags 2022-12-19 23:20:11 +01:00
tools build: generate files with go:build tags 2022-12-19 23:20:11 +01:00
transform transform: remove duplicate if in gc transform 2022-11-18 20:19:47 +01:00
.dockerignore docker: apt clean before apt get of llvm to avoid broken packages 2021-08-18 20:01:50 +02:00
.gitignore all: git ignore smoketest output 2022-07-08 13:01:14 +02:00
.gitmodules Revert "Bump CMSIS to 5.9.0" 2022-12-16 21:26:49 +01:00
BUILDING.md all: drop support for Go 1.16 and Go 1.17 2022-08-30 12:38:06 +02:00
CHANGELOG.md all: update to version 0.26.0 2022-09-29 15:05:15 +02:00
CODE-OF-CONDUCT.md docs: add official code of conduct using 'Contributor Covenant' 2019-12-04 21:53:46 +01:00
colorwriter.go all: implement gdb sub-command for easy debugging 2018-10-03 19:03:22 +02:00
CONTRIBUTING.md docs: update CONTRIBUTING links to point to web site. Also replace Azure build badge with Windows build on GH Actions. 2021-11-18 17:49:13 -05:00
CONTRIBUTORS update my name in the contributors list 2020-09-12 16:51:47 +02:00
corpus_test.go src/testing: add support for -benchmem 2022-08-20 11:41:20 +02:00
Dockerfile avr: drop GNU toolchain dependency 2022-11-06 09:05:05 +01:00
go.mod compiler: update golang.org/x/tools/ssa 2023-01-14 22:08:38 +01:00
go.sum compiler: update golang.org/x/tools/ssa 2023-01-14 22:08:38 +01:00
LICENSE all: update license year to 2022 2022-01-25 17:13:34 +01:00
main.go Allows the emulator to expand {tmpDir} 2023-01-19 20:06:18 +01:00
main_test.go test: print package name when compilation failed 2023-01-15 08:49:18 +01:00
Makefile builder: add support for Go 1.20 2023-01-17 08:38:54 +01:00
monitor.go main: allow setting the baud rate for serial monitors (#3190) 2022-09-24 19:09:41 +02:00
README.md docs: update README with missing boards 2023-01-11 21:51:03 +01:00
util_unix.go build: drop deprecated build tags 2022-12-19 23:20:11 +01:00
util_windows.go gdb: support daemonization on windows 2021-03-04 14:46:10 +01:00

TinyGo - Go compiler for small places

Linux macOS Windows Docker CircleCI

TinyGo is a Go compiler intended for use in small places such as microcontrollers, WebAssembly (Wasm), and command-line tools.

It reuses libraries used by the Go language tools alongside LLVM to provide an alternative way to compile programs written in the Go programming language.

Here is an example program that blinks the built-in LED when run directly on any supported board with onboard LED:

package main

import (
    "machine"
    "time"
)

func main() {
    led := machine.LED
    led.Configure(machine.PinConfig{Mode: machine.PinOutput})
    for {
        led.Low()
        time.Sleep(time.Millisecond * 1000)

        led.High()
        time.Sleep(time.Millisecond * 1000)
    }
}

The above program can be compiled and run without modification on an Arduino Uno, an Adafruit ItsyBitsy M0, or any of the supported boards that have a built-in LED, just by setting the correct TinyGo compiler target. For example, this compiles and flashes an Arduino Uno:

tinygo flash -target arduino examples/blinky1

Installation

See the getting started instructions for information on how to install TinyGo, as well as how to run the TinyGo compiler using our Docker container.

Supported boards/targets

You can compile TinyGo programs for microcontrollers, WebAssembly and Linux.

The following 94 microcontroller boards are currently supported:

For more information, see this list of boards. Pull requests for additional support are welcome!

Currently supported features:

For a description of currently supported Go language features, please see https://tinygo.org/lang-support/.

Documentation

Documentation is located on our web site at https://tinygo.org/.

You can find the web site code at https://github.com/tinygo-org/tinygo-site.

Getting help

If you're looking for a more interactive way to discuss TinyGo usage or development, we have a #TinyGo channel on the Gophers Slack.

If you need an invitation for the Gophers Slack, you can generate one here which should arrive fairly quickly (under 1 min): https://invite.slack.golangbridge.org

Contributing

Your contributions are welcome!

Please take a look at our Contributing page on our web site for details.

Project Scope

Goals:

  • Have very small binary sizes. Don't pay for what you don't use.
  • Support for most common microcontroller boards.
  • Be usable on the web using WebAssembly.
  • Good CGo support, with no more overhead than a regular function call.
  • Support most standard library packages and compile most Go code without modification.

Non-goals:

  • Be efficient while using zillions of goroutines. However, good goroutine support is certainly a goal.
  • Be as fast as gc. However, LLVM will probably be better at optimizing certain things so TinyGo might actually turn out to be faster for number crunching.
  • Be able to compile every Go program out there.

Why this project exists

We never expected Go to be an embedded language and so its got serious problems...

-- Rob Pike, GopherCon 2014 Opening Keynote

TinyGo is a project to bring Go to microcontrollers and small systems with a single processor core. It is similar to emgo but a major difference is that we want to keep the Go memory model (which implies garbage collection of some sort). Another difference is that TinyGo uses LLVM internally instead of emitting C, which hopefully leads to smaller and more efficient code and certainly leads to more flexibility.

The original reasoning was: if Python can run on microcontrollers, then certainly Go should be able to run on even lower level micros.

License

This project is licensed under the BSD 3-clause license, just like the Go project itself.

Some code has been copied from the LLVM project and is therefore licensed under a variant of the Apache 2.0 license. This has been clearly indicated in the header of these files.

Some code has been copied and/or ported from Paul Stoffregen's Teensy libraries and is therefore licensed under PJRC's license. This has been clearly indicated in the header of these files.