![]() This commit improves accuracy of the -size=full flag in a big way. Instead of relying on symbol names to figure out by which package symbols belong, it will instead mostly use DWARF debug information (specifically, debug line tables and debug information for global variables) relying on symbols only for some specific things. This is much more accurate: it also accounts for inlined functions. For example, here is how it looked previously when compiling a personal project: code rodata data bss | flash ram | package 1902 333 0 0 | 2235 0 | (bootstrap) 46 256 0 0 | 302 0 | github 0 454 0 0 | 454 0 | handleHardFault$string 154 24 4 4 | 182 8 | internal/task 2498 83 5 2054 | 2586 2059 | machine 0 16 24 130 | 40 154 | machine$alloc 1664 32 12 8 | 1708 20 | main 0 0 0 200 | 0 200 | main$alloc 2476 79 0 36 | 2555 36 | runtime 576 0 0 0 | 576 0 | tinygo 9316 1277 45 2432 | 10638 2477 | (sum) 11208 - 48 6548 | 11256 6596 | (all) And here is how it looks now: code rodata data bss | flash ram | package ------------------------------- | --------------- | ------- 1509 0 12 23 | 1521 35 | (unknown) 660 0 0 0 | 660 0 | C compiler-rt 58 0 0 0 | 58 0 | C picolibc 0 0 0 4096 | 0 4096 | C stack 174 0 0 0 | 174 0 | device/arm 6 0 0 0 | 6 0 | device/sam 598 256 0 0 | 854 0 | github.com/aykevl/ledsgo 320 24 0 4 | 344 4 | internal/task 1414 99 24 2181 | 1537 2205 | machine 726 352 12 208 | 1090 220 | main 3002 542 0 36 | 3544 36 | runtime 848 0 0 0 | 848 0 | runtime/volatile 70 0 0 0 | 70 0 | time 550 0 0 0 | 550 0 | tinygo.org/x/drivers/ws2812 ------------------------------- | --------------- | ------- 9935 1273 48 6548 | 11256 6596 | total There are some notable differences: * Odd packages like main$alloc and handleHardFault$string are gone, instead their code is put in the correct package. * C libraries and the stack are now included in the list, they were previously part of the (bootstrap) pseudo-package. * Unknown bytes are slightly reduced. It should be possible to reduce it significantly more in the future: most of it is now caused by interface invoke wrappers. * Inlined functions are now correctly attributed. For example, the runtime/volatile package is normally entirely inlined. * There is no difference between (sum) and (all) anymore. A better code size algorithm now counts the code/data sizes correctly. * And last (but not least) there is a stylistic change: the table now looks more like a table. Especially the summary should be clearer now. Future goals: * Improve debug information so that the (unknown) pseudo-package is reduced in size or even eliminated altogether. * Add support for other file formats, most importantly WebAssembly. * Perhaps provide a way to expand this report per file, or in a machine-readable format like JSON or CSV. |
||
---|---|---|
.circleci | ||
.github/workflows | ||
bin | ||
builder | ||
cgo | ||
compileopts | ||
compiler | ||
docs | ||
goenv | ||
hooks | ||
interp | ||
lib | ||
loader | ||
src | ||
stacksize | ||
targets | ||
testdata | ||
tests | ||
tools | ||
transform | ||
.dockerignore | ||
.gitignore | ||
.gitmodules | ||
azure-pipelines.yml | ||
BUILDING.md | ||
CHANGELOG.md | ||
CODE-OF-CONDUCT.md | ||
colorwriter.go | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
main_test.go | ||
Makefile | ||
README.md | ||
util_unix.go | ||
util_windows.go |
TinyGo - Go compiler for small places
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 71 microcontroller boards are currently supported:
- Adafruit Circuit Playground Bluefruit
- Adafruit Circuit Playground Express
- Adafruit CLUE
- Adafruit Feather M0
- Adafruit Feather M4
- Adafruit Feather M4 CAN
- Adafruit Feather nRF52840 Express
- Adafruit Feather nRF52840 Sense
- Adafruit Feather RP2040
- Adafruit Feather STM32F405 Express
- Adafruit Grand Central M4
- Adafruit ItsyBitsy M0
- Adafruit ItsyBitsy M4
- Adafruit ItsyBitsy nRF52840
- Adafruit Matrix Portal M4
- Adafruit Metro M4 Express Airlift
- Adafruit PyBadge
- Adafruit PyGamer
- Adafruit PyPortal
- Adafruit QT Py
- Adafruit Trinket M0
- Arduino Mega 1280
- Arduino Mega 2560
- Arduino MKR1000
- Arduino MKR WiFi 1010
- Arduino Nano
- Arduino Nano 33 BLE
- Arduino Nano 33 BLE Sense
- Arduino Nano 33 IoT
- Arduino Nano RP2040 Connect
- Arduino Uno
- Arduino Zero
- BBC micro:bit
- BBC micro:bit v2
- Digispark
- Dragino LoRaWAN GPS Tracker LGT-92
- ESP32
- ESP8266
- Game Boy Advance
- M5Stack Core2
- Makerdiary nRF52840-MDK
- Makerdiary nRF52840-MDK USB Dongle
- Microchip SAM E54 Xplained Pro
- nice!nano
- Nintendo Switch
- Nordic Semiconductor PCA10031
- Nordic Semiconductor PCA10040
- Nordic Semiconductor PCA10056
- Nordic Semiconductor pca10059
- Particle Argon
- Particle Boron
- Particle Xenon
- Phytec reel board
- PineTime DevKit
- PJRC Teensy 3.6
- PJRC Teensy 4.0
- ProductivityOpen P1AM-100
- Raspberry Pi Pico
- Raytac MDBT50Q-RX Dongle (with TinyUF2 bootloader)
- Seeed Wio Terminal
- Seeed Seeeduino XIAO
- Seeed Sipeed MAix BiT
- SiFIve HiFive1
- ST Micro "Nucleo" F103RB
- ST Micro "Nucleo" F722ZE
- ST Micro "Nucleo" L031K6
- ST Micro "Nucleo" L432KC
- ST Micro "Nucleo" L552ZE
- ST Micro STM32F103XX "Bluepill"
- ST Micro STM32F407 "Discovery"
- X9 Pro smartwatch
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.md document 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:
- Using more than one core.
- 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.