github
/
tinygo
mirror of https://github.com/tinygo-org/tinygo.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2604 Commits
99 Branches
41 Tags
26 MiB
Tree: d139fa5e0f
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd139fa5e0f'
${ noResults }
tinygo/Makefile

660 lines
32 KiB
Raw Normal View History

Hello world!
7 years ago
Makefile cleanup
7 years ago
# aliases
Makefile: rename tgo to tinygo
6 years ago
all: tinygo
Hello world!
7 years ago
Makefile: automatically build LLVM when needed
6 years ago
# Default build and source directories, as created by `make llvm-build`.
LLVM_BUILDDIR ?= llvm-build
Makefile: allow overriding the llvm-project directory This allows setting a different directory for experimental changes. For example, I also have a llvm-project.master directory that tracks the master branch. It is very useful to be able to temporarily use that directory: make llvm-build.master LLVM_BUILDDIR=llvm-build.master LLVM_PROJECT=llvm-project.master
5 years ago
LLVM_PROJECTDIR ?= llvm-project
CLANG_SRC ?= $(LLVM_PROJECTDIR)/clang
LLD_SRC ?= $(LLVM_PROJECTDIR)/lld
Makefile: automatically build LLVM when needed
6 years ago
Makefile: fix LLVM tools detection for wasi-libc This makes the `make wasi-libc` command much more reliable and makes the CI configuration simpler. Also, it avoids warnings when they are not relevant.
5 years ago
# Try to autodetect LLVM build tools.
Makefile: reorganize tool detection There are now a large number of paths that need to be searched, and this started to get a little bit unwieldy. Additionally, brew paths were searched unconditionally, resulting in warnings every time the Makefile was run. This reorganizes the detection paths into a parameterized list of search paths by version, which is appended to on Mac. This list is then expanded across all versions. The loop and filtering has been moved into the detect function. Additionally, a helpful error message is displayed upon use of a missing tool: Makefile:204: *** failed to locate llvm-blah at any of: llvm-build/bin/llvm-blah llvm-blah-13 llvm-blah-12 llvm-blah-11 llvm-blah. Stop.
3 years ago
# Versions are listed here in descending priority order.
LLVM_VERSIONS = 13 12 11
errifempty = $(if $(1),$(1),$(error $(2)))
Makefile: fix tool autodetect conversion to absolute path After the last change, $(abspath x) no longer returned the actual absolute path. This uses which instead.
3 years ago
detect = $(shell which $(call errifempty,$(firstword $(foreach p,$(2),$(shell command -v $(p) 2> /dev/null && echo $(p)))),failed to locate $(1) at any of: $(2)))
Makefile: reorganize tool detection There are now a large number of paths that need to be searched, and this started to get a little bit unwieldy. Additionally, brew paths were searched unconditionally, resulting in warnings every time the Makefile was run. This reorganizes the detection paths into a parameterized list of search paths by version, which is appended to on Mac. This list is then expanded across all versions. The loop and filtering has been moved into the detect function. Additionally, a helpful error message is displayed upon use of a missing tool: Makefile:204: *** failed to locate llvm-blah at any of: llvm-build/bin/llvm-blah llvm-blah-13 llvm-blah-12 llvm-blah-11 llvm-blah. Stop.
3 years ago
toolSearchPathsVersion = $(1)-$(2)
ifeq ($(shell uname -s),Darwin)
# Also explicitly search Brew's copy, which is not in PATH by default.
BREW_PREFIX := $(shell brew --prefix)
toolSearchPathsVersion += $(BREW_PREFIX)/opt/llvm@$(2)/bin/$(1)-$(2) $(BREW_PREFIX)/opt/llvm@$(2)/bin/$(1)
endif
# First search for a custom built copy, then move on to explicitly version-tagged binaries, then just see if the tool is in path with its normal name.
Makefile: use absolute path for llvm-build/bin/* binaries This un-breaks `make wasi-libc` on my system.
3 years ago
findLLVMTool = $(call detect,$(1),$(abspath llvm-build/bin/$(1)) $(foreach ver,$(LLVM_VERSIONS),$(call toolSearchPathsVersion,$(1),$(ver))) $(1))
Makefile: reorganize tool detection There are now a large number of paths that need to be searched, and this started to get a little bit unwieldy. Additionally, brew paths were searched unconditionally, resulting in warnings every time the Makefile was run. This reorganizes the detection paths into a parameterized list of search paths by version, which is appended to on Mac. This list is then expanded across all versions. The loop and filtering has been moved into the detect function. Additionally, a helpful error message is displayed upon use of a missing tool: Makefile:204: *** failed to locate llvm-blah at any of: llvm-build/bin/llvm-blah llvm-blah-13 llvm-blah-12 llvm-blah-11 llvm-blah. Stop.
3 years ago
CLANG ?= $(call findLLVMTool,clang)
LLVM_AR ?= $(call findLLVMTool,llvm-ar)
LLVM_NM ?= $(call findLLVMTool,llvm-nm)
wasm: include wasi-libc This allows CGo code to call some libc functions. Additionally, by putting memset/memmove/memcpy in an archive they're not included anymore when not necessary, reducing code size for small programs.
5 years ago
allow selecting a different go version and use ccache for LLVM whenever possible
5 years ago
# Go binary and GOROOT to select
GO ?= go
export GOROOT = $(shell $(GO) env GOROOT)
ci: move all cross compilation tests to Linux The idea here is as follows: - Run all Linux and cross compilation tests in the asser-test-linux job. - Only run native tests on MacOS and Windows. This reduces testing time on MacOS and Windows, which are generally more expensive in CI. Also, by not duplicating tests in Windows and MacOS we can reduce overall CI usage a bit. I've also changed the assert-test-linux job a bit to so that the tests that are more likely to break and the tests that are only run in assert-test-linux are run first.
3 years ago
# Flags to pass to go test.
GOTESTFLAGS ?= -v
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
# md5sum binary
MD5SUM = md5sum
try adding assertions to CI
5 years ago
# tinygo binary for tests
Makefile: detected TINYGO now works even if a rule changes directory
3 years ago
TINYGO ?= $(call detect,tinygo,tinygo $(CURDIR)/build/tinygo)
try adding assertions to CI
5 years ago
allow selecting a different go version and use ccache for LLVM whenever possible
5 years ago
# Use CCACHE for LLVM if possible
Makefile: autodetect llvm-ar and llvm-nm commands
5 years ago
ifneq (, $(shell command -v ccache 2> /dev/null))
try adding assertions to CI
5 years ago
LLVM_OPTION += '-DLLVM_CCACHE_BUILD=ON'
endif
# Allow enabling LLVM assertions
ifeq (1, $(ASSERT))
LLVM_OPTION += '-DLLVM_ENABLE_ASSERTIONS=ON'
else
LLVM_OPTION += '-DLLVM_ENABLE_ASSERTIONS=OFF'
allow selecting a different go version and use ccache for LLVM whenever possible
5 years ago
endif
add rp2040, pico adds preliminary support (just enough to run blinky1) for the Raspberry Pi Pico board along with the rp2040 mcu.
4 years ago
.PHONY: all tinygo test $(LLVM_BUILDDIR) llvm-source clean fmt gen-device gen-device-nrf gen-device-nxp gen-device-avr gen-device-rp
Makefile: using an alternative LLVM build dir now works
6 years ago
all: add support for windows/amd64 This uses Mingw-w64, which seems to be the de facto standard for porting Unixy programs to Windows.
3 years ago
LLVM_COMPONENTS = all-targets analysis asmparser asmprinter bitreader bitwriter codegen core coroutines coverage debuginfodwarf debuginfopdb executionengine frontendopenmp instrumentation interpreter ipo irreader libdriver linker lto mc mcjit objcarcopts option profiledata scalaropts support target windowsmanifest
all: add static and release Makefile targets
6 years ago
all: add support for Windows
6 years ago
ifeq ($(OS),Windows_NT)
EXE = .exe
circleci: do macOS builds here instead of on Travis CI This provides several advantages. Among others: * Much faster and hopefully more reliable. * Good caching support to store LLVM builds. * Building and testing of release-ready artifacts.
6 years ago
START_GROUP = -Wl,--start-group
END_GROUP = -Wl,--end-group
all: add support for Windows
6 years ago
# LLVM compiled using MinGW on Windows appears to have problems with threads.
# Without this flag, linking results in errors like these:
# libLLVMSupport.a(Threading.cpp.obj):Threading.cpp:(.text+0x55): undefined reference to `std::thread::hardware_concurrency()'
all: switch to LLVM 11 for static builds This commit switches to LLVM 11 for builds with LLVM linked statically (e.g. `make`). It does not yet switch the default for builds dynamically linked to LLVM, that should be done in a later change. This commit also changes to use the default host toolchain (probably GCC) instead of Clang as the default compiler in CI. There were some issues with Clang 3.8 in CI and hopefully this will fix it. Additionally it updates the way LLVM is built on Windows, with -DLLVM_ENABLE_PIC=OFF (which should have been used all along). This change makes it possible to revert a hack to build libclang manually and instead uses the libclang static library like on all other operating systems, simplifying the Makefile.
4 years ago
LLVM_OPTION += -DLLVM_ENABLE_THREADS=OFF -DLLVM_ENABLE_PIC=OFF
all: add support for Windows
6 years ago
all: switch to LLVM 11 for static builds This commit switches to LLVM 11 for builds with LLVM linked statically (e.g. `make`). It does not yet switch the default for builds dynamically linked to LLVM, that should be done in a later change. This commit also changes to use the default host toolchain (probably GCC) instead of Clang as the default compiler in CI. There were some issues with Clang 3.8 in CI and hopefully this will fix it. Additionally it updates the way LLVM is built on Windows, with -DLLVM_ENABLE_PIC=OFF (which should have been used all along). This change makes it possible to revert a hack to build libclang manually and instead uses the libclang static library like on all other operating systems, simplifying the Makefile.
4 years ago
CGO_CPPFLAGS += -DCINDEX_NO_EXPORTS
all: add support for Windows
6 years ago
CGO_LDFLAGS += -static -static-libgcc -static-libstdc++
CGO_LDFLAGS_EXTRA += -lversion
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
USE_SYSTEM_BINARYEN ?= 1
internal/task: use asyncify on webassembly This change implements a new "scheduler" for WebAssembly using binaryen's asyncify transform. This is more reliable than the current "coroutines" transform, and works with non-Go code in the call stack. runtime (js/wasm): handle scheduler nesting If WASM calls into JS which calls back into WASM, it is possible for the scheduler to nest. The event from the callback must be handled immediately, so the task cannot simply be deferred to the outer scheduler. This creates a minimal scheduler loop which is used to handle such nesting.
3 years ago
all: add support for Windows
6 years ago
else ifeq ($(shell uname -s),Darwin)
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
MD5SUM = md5
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
USE_SYSTEM_BINARYEN ?= 1
Add initial FreeBSD support
5 years ago
else ifeq ($(shell uname -s),FreeBSD)
MD5SUM = md5
START_GROUP = -Wl,--start-group
END_GROUP = -Wl,--end-group
all: add support for Windows
6 years ago
else
START_GROUP = -Wl,--start-group
END_GROUP = -Wl,--end-group
circleci: do macOS builds here instead of on Travis CI This provides several advantages. Among others: * Much faster and hopefully more reliable. * Good caching support to store LLVM builds. * Building and testing of release-ready artifacts.
6 years ago
endif
ci: only build the necessary LLVM libraries and tools This should improve rebuild time, but perhaps more importantly massively reduces cache size which then reduces incremental build time.
4 years ago
# Libraries that should be linked in for the statically linked Clang.
ci: disable building some optional Clang components This commit disables the Clang static analyzer and ARCMigrate components of Clang. These aren't used at the moment in TinyGo so don't need to be enabled. This reduces the build by 200 files (2909 -> 2709). The idea comes from here (via LLVM weekly): https://www.cambus.net/speedbuilding-llvm-clang-in-5-minutes/
4 years ago
CLANG_LIB_NAMES = clangAnalysis clangAST clangASTMatchers clangBasic clangCodeGen clangCrossTU clangDriver clangDynamicASTMatchers clangEdit clangFormat clangFrontend clangFrontendTool clangHandleCXX clangHandleLLVM clangIndex clangLex clangParse clangRewrite clangRewriteFrontend clangSema clangSerialization clangTooling clangToolingASTDiff clangToolingCore clangToolingInclusions
ci: only build the necessary LLVM libraries and tools This should improve rebuild time, but perhaps more importantly massively reduces cache size which then reduces incremental build time.
4 years ago
CLANG_LIBS = $(START_GROUP) $(addprefix -l,$(CLANG_LIB_NAMES)) $(END_GROUP) -lstdc++
all: add static and release Makefile targets
6 years ago
ci: only build the necessary LLVM libraries and tools This should improve rebuild time, but perhaps more importantly massively reduces cache size which then reduces incremental build time.
4 years ago
# Libraries that should be linked in for the statically linked LLD.
LLD_LIB_NAMES = lldCOFF lldCommon lldCore lldDriver lldELF lldMachO lldMinGW lldReaderWriter lldWasm lldYAML
LLD_LIBS = $(START_GROUP) $(addprefix -l,$(LLD_LIB_NAMES)) $(END_GROUP)
main: optionally build with LLD When building statically against LLVM, LLD is also included now. When included, the built in wasm-ld will automatically be used instead of the external command. There is also support for linking ELF files but because lld does not fully support armv6m this is not yet enabled (it produces a warning).
6 years ago
ci: only build the necessary LLVM libraries and tools This should improve rebuild time, but perhaps more importantly massively reduces cache size which then reduces incremental build time.
4 years ago
# Other libraries that are needed to link TinyGo.
EXTRA_LIB_NAMES = LLVMInterpreter
all: add LLVM 12 support Originally based on a PR by @QuLogic, but extended a lot to get all tests to pass.
4 years ago
# All libraries to be built and linked with the tinygo binary (lib/lib*.a).
LIB_NAMES = clang $(CLANG_LIB_NAMES) $(LLD_LIB_NAMES) $(EXTRA_LIB_NAMES)
ci: only build the necessary LLVM libraries and tools This should improve rebuild time, but perhaps more importantly massively reduces cache size which then reduces incremental build time.
4 years ago
# These build targets appear to be the only ones necessary to build all TinyGo
# dependencies. Only building a subset significantly speeds up rebuilding LLVM.
# The Makefile rules convert a name like lldELF to lib/liblldELF.a to match the
# library path (for ninja).
# This list also includes a few tools that are necessary as part of the full
# TinyGo build.
all: add LLVM 12 support Originally based on a PR by @QuLogic, but extended a lot to get all tests to pass.
4 years ago
NINJA_BUILD_TARGETS = clang llvm-config llvm-ar llvm-nm $(addprefix lib/lib,$(addsuffix .a,$(LIB_NAMES)))
main: optionally build with LLD When building statically against LLVM, LLD is also included now. When included, the built in wasm-ld will automatically be used instead of the external command. There is also support for linking ELF files but because lld does not fully support armv6m this is not yet enabled (it produces a warning).
6 years ago
all: add static and release Makefile targets
6 years ago
# For static linking.
all: add support for Windows
6 years ago
ifneq ("$(wildcard $(LLVM_BUILDDIR)/bin/llvm-config*)","")
all: switch to LLVM 11 for static builds This commit switches to LLVM 11 for builds with LLVM linked statically (e.g. `make`). It does not yet switch the default for builds dynamically linked to LLVM, that should be done in a later change. This commit also changes to use the default host toolchain (probably GCC) instead of Clang as the default compiler in CI. There were some issues with Clang 3.8 in CI and hopefully this will fix it. Additionally it updates the way LLVM is built on Windows, with -DLLVM_ENABLE_PIC=OFF (which should have been used all along). This change makes it possible to revert a hack to build libclang manually and instead uses the libclang static library like on all other operating systems, simplifying the Makefile.
4 years ago
CGO_CPPFLAGS+=$(shell $(LLVM_BUILDDIR)/bin/llvm-config --cppflags) -I$(abspath $(LLVM_BUILDDIR))/tools/clang/include -I$(abspath $(CLANG_SRC))/include -I$(abspath $(LLD_SRC))/include
main: switch to LLVM 10 This commit also adds a bit of version independence, in particular for external commands. It also adds the LLVM version to the `tinygo version` command, which might help while debugging.
5 years ago
CGO_CXXFLAGS=-std=c++14
all: add LLVM 12 support Originally based on a PR by @QuLogic, but extended a lot to get all tests to pass.
4 years ago
CGO_LDFLAGS+=-L$(abspath $(LLVM_BUILDDIR)/lib) -lclang $(CLANG_LIBS) $(LLD_LIBS) $(shell $(LLVM_BUILDDIR)/bin/llvm-config --ldflags --libs --system-libs $(LLVM_COMPONENTS)) -lstdc++ $(CGO_LDFLAGS_EXTRA)
Makefile: use the LLVM monorepo The -DLLVM_TOOL_CLANG_TOOLS_EXTRA_BUILD=OFF option turning off the building of the extra clang tools is required, otherwise linking the tinygo binary fails.
5 years ago
endif
all: add static and release Makefile targets
6 years ago
Hello world!
7 years ago
clean:
@rm -rf build
Be able to actually run the blinky example on an nRF runtime.Sleep() doesn't work yet so it prints a lot of data. Also, this depends on a small patch to nrfx.
7 years ago
Makefile: add src/testing to FMT_PATHS
3 years ago
FMT_PATHS = ./*.go builder cgo compiler interp loader src/device/arm src/examples src/machine src/os src/reflect src/runtime src/sync src/syscall src/testing src/internal/reflectlite transform
Add make fmt
6 years ago
fmt:
all: check formatting on CI
6 years ago
@gofmt -l -w $(FMT_PATHS)
fmt-check:
@unformatted=$$(gofmt -l $(FMT_PATHS)); [ -z "$$unformatted" ] && exit 0; echo "Unformatted:"; for fn in $$unformatted; do echo " $$fn"; done; exit 1
Add make fmt
6 years ago
Add test command to tinygo (#243) * Add test command to tinygo
5 years ago
add rp2040, pico adds preliminary support (just enough to run blinky1) for the Raspberry Pi Pico board along with the rp2040 mcu.
4 years ago
gen-device: gen-device-avr gen-device-esp gen-device-nrf gen-device-sam gen-device-sifive gen-device-kendryte gen-device-nxp gen-device-rp
Group together STM32 smoke tests. And then allow them to be disabled with one option.
4 years ago
ifneq ($(STM32), 0)
gen-device: gen-device-stm32
endif
Be able to actually run the blinky example on an nRF runtime.Sleep() doesn't work yet so it prints a lot of data. Also, this depends on a small patch to nrfx.
7 years ago
avr: remove device files, use them from a subrepository These files don't really belong in this repository. It's better to generate them automatically from a source, like the one provided by the avr-rust project. So a new command `make gen-device-avr` has been provided for this purpose.
6 years ago
gen-device-avr:
Makefile: check whether submodules have been downloaded in some common cases This should help new people making this very common mistake.
4 years ago
@if [ ! -e lib/avr/README.md ]; then echo "Submodules have not been downloaded. Please download them using:\n git submodule update --init"; exit 1; fi
tools: rewrite gen-device-avr in Go This brings a big speedup. Not counting gofmt time, `make gen-device-avr` became about 3x faster. In the future, it might be an idea to generate the AST in-memory and write it out already formatted.
5 years ago
$(GO) build -o ./build/gen-device-avr ./tools/gen-device-avr/
./build/gen-device-avr lib/avr/packs/atmega src/device/avr/
./build/gen-device-avr lib/avr/packs/tiny src/device/avr/
@GO111MODULE=off $(GO) fmt ./src/device/avr
avr: remove device files, use them from a subrepository These files don't really belong in this repository. It's better to generate them automatically from a source, like the one provided by the avr-rust project. So a new command `make gen-device-avr` has been provided for this purpose.
6 years ago
tools: rewrite gen-device-svd in Go This should make it more maintainable. Another big advantage that generation time (including gofmt) is now 3 times faster. No real attempt at refactoring has been made, that will need to be done at a later time.
5 years ago
build/gen-device-svd: ./tools/gen-device-svd/*.go
$(GO) build -o $@ ./tools/gen-device-svd/
esp: add support for the Espressif ESP32 chip This is only very minimal support. More support (such as tinygo flash, or peripheral access) should be added in later commits, to keep this one focused. Importantly, this commit changes the LLVM repo from llvm/llvm-project to tinygo-org/llvm-project. This provides a little bit of versioning in case something changes in the Espressif fork. If we want to upgrade to LLVM 11 it's easy to switch back to llvm/llvm-project until Espressif has updated their fork.
4 years ago
gen-device-esp: build/gen-device-svd
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/Espressif-Community -interrupts=software lib/cmsis-svd/data/Espressif-Community/ src/device/esp/
esp32c3: add support for this chip This change adds support for the ESP32-C3, a new chip from Espressif. It is a RISC-V core so porting was comparatively easy. Most peripherals are shared with the (original) ESP32 chip, but with subtle differences. Also, the SVD file I've used gives some peripherals/registers a different name which makes sharing code harder. Eventually, when an official SVD file for the ESP32 is released, I expect that a lot of code can be shared between the two chips. More information: https://www.espressif.com/en/products/socs/esp32-c3 TODO: - stack scheduler - interrupts - most peripherals (SPI, I2C, PWM, etc)
3 years ago
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/Espressif -interrupts=software lib/cmsis-svd/data/Espressif/ src/device/esp/
esp: add support for the Espressif ESP32 chip This is only very minimal support. More support (such as tinygo flash, or peripheral access) should be added in later commits, to keep this one focused. Importantly, this commit changes the LLVM repo from llvm/llvm-project to tinygo-org/llvm-project. This provides a little bit of versioning in case something changes in the Espressif fork. If we want to upgrade to LLVM 11 it's easy to switch back to llvm/llvm-project until Espressif has updated their fork.
4 years ago
GO111MODULE=off $(GO) fmt ./src/device/esp
tools: rewrite gen-device-svd in Go This should make it more maintainable. Another big advantage that generation time (including gofmt) is now 3 times faster. No real attempt at refactoring has been made, that will need to be done at a later time.
5 years ago
gen-device-nrf: build/gen-device-svd
./build/gen-device-svd -source=https://github.com/NordicSemiconductor/nrfx/tree/master/mdk lib/nrfx/mdk/ src/device/nrf/
all: add support for go 1.13
5 years ago
GO111MODULE=off $(GO) fmt ./src/device/nrf
Makefile: add gen-device-stm32 to gen-device target
6 years ago
Minimal NXP/Teensy support
5 years ago
gen-device-nxp: build/gen-device-svd
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/NXP lib/cmsis-svd/data/NXP/ src/device/nxp/
GO111MODULE=off $(GO) fmt ./src/device/nxp
tools: rewrite gen-device-svd in Go This should make it more maintainable. Another big advantage that generation time (including gofmt) is now 3 times faster. No real attempt at refactoring has been made, that will need to be done at a later time.
5 years ago
gen-device-sam: build/gen-device-svd
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/Atmel lib/cmsis-svd/data/Atmel/ src/device/sam/
all: add support for go 1.13
5 years ago
GO111MODULE=off $(GO) fmt ./src/device/sam
generator: generate device wrappers for Atmel SAM family Signed-off-by: Ron Evans <ron@hybridgroup.com>
6 years ago
tools: rewrite gen-device-svd in Go This should make it more maintainable. Another big advantage that generation time (including gofmt) is now 3 times faster. No real attempt at refactoring has been made, that will need to be done at a later time.
5 years ago
gen-device-sifive: build/gen-device-svd
runtime/fe310: add support for PLIC interrupts This commit adds support for software vectoring in the PLIC interrupt. The interrupt table is created by the compiler, which leads to very compact code while retaining the flexibility that the interrupt API provides.
5 years ago
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/SiFive-Community -interrupts=software lib/cmsis-svd/data/SiFive-Community/ src/device/sifive/
all: add support for go 1.13
5 years ago
GO111MODULE=off $(GO) fmt ./src/device/sifive
all: add HiFive1 rev B board with RISC-V architecture This page has been a big help in adding support for this new chip: https://wiki.osdev.org/HiFive-1_Bare_Bones
6 years ago
Add new kendryte k210 target definition
5 years ago
gen-device-kendryte: build/gen-device-svd
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/Kendryte-Community -interrupts=software lib/cmsis-svd/data/Kendryte-Community/ src/device/kendryte/
GO111MODULE=off $(GO) fmt ./src/device/kendryte
tools: rewrite gen-device-svd in Go This should make it more maintainable. Another big advantage that generation time (including gofmt) is now 3 times faster. No real attempt at refactoring has been made, that will need to be done at a later time.
5 years ago
gen-device-stm32: build/gen-device-svd
stm32: use stm32-rs SVDs which are of much higher quality This commit changes the number of wait states for the stm32f103 chip to 2 instead of 4. This gets it back in line with the datasheet, but it also has the side effect of breaking I2C. Therefore, another (seemingly unrelated) change is needed: the i2cTimeout constant must be increased to a higher value to adjust to the lower flash wait states - presumably because the lower number of wait states allows the chip to run code faster.
4 years ago
./build/gen-device-svd -source=https://github.com/tinygo-org/stm32-svd lib/stm32-svd/svd src/device/stm32/
all: add support for go 1.13
5 years ago
GO111MODULE=off $(GO) fmt ./src/device/stm32
stm32: initial support
6 years ago
add rp2040, pico adds preliminary support (just enough to run blinky1) for the Raspberry Pi Pico board along with the rp2040 mcu.
4 years ago
gen-device-rp: build/gen-device-svd
./build/gen-device-svd -source=https://github.com/posborne/cmsis-svd/tree/master/data/RaspberryPi lib/cmsis-svd/data/RaspberryPi/ src/device/rp/
GO111MODULE=off $(GO) fmt ./src/device/rp
Makefile: automatically build LLVM when needed
6 years ago
# Get LLVM sources.
ci: improve llvm-source cache
4 years ago
$(LLVM_PROJECTDIR)/llvm:
all: switch to LLVM 13 This adds support for building with `-tags=llvm13` and switches to LLVM 13 for tinygo binaries that are statically linked against LLVM. Some notes on this commit: * Added `-mfloat-abi=soft` to all Cortex-M targets because otherwise nrfx would complain that floating point was enabled on Cortex-M0. That's not the case, but with `-mfloat-abi=soft` the `__SOFTFP__` macro is defined which silences this warning. See: https://reviews.llvm.org/D100372 * Changed from `--sysroot=<root>` to `-nostdlib -isystem <root>` for musl because with Clang 13, even with `--sysroot` some system libraries are used which we don't want. * Changed all `-Xclang -internal-isystem -Xclang` to simply `-isystem`, for consistency with the above change. It appears to have the same effect. * Moved WebAssembly function declarations to the top of the file in task_asyncify_wasm.S because (apparently) the assembler has become more strict.
3 years ago
git clone -b xtensa_release_13.0.0 --depth=1 https://github.com/tinygo-org/llvm-project $(LLVM_PROJECTDIR)
ci: improve llvm-source cache
4 years ago
llvm-source: $(LLVM_PROJECTDIR)/llvm
Makefile: automatically build LLVM when needed
6 years ago
# Configure LLVM.
Makefile: using an alternative LLVM build dir now works
6 years ago
TINYGO_SOURCE_DIR=$(shell pwd)
$(LLVM_BUILDDIR)/build.ninja: llvm-source
internal/task: use asyncify on webassembly This change implements a new "scheduler" for WebAssembly using binaryen's asyncify transform. This is more reliable than the current "coroutines" transform, and works with non-Go code in the call stack. runtime (js/wasm): handle scheduler nesting If WASM calls into JS which calls back into WASM, it is possible for the scheduler to nest. The event from the callback must be handled immediately, so the task cannot simply be deferred to the outer scheduler. This creates a minimal scheduler loop which is used to handle such nesting.
3 years ago
mkdir -p $(LLVM_BUILDDIR) && cd $(LLVM_BUILDDIR) && cmake -G Ninja $(TINYGO_SOURCE_DIR)/$(LLVM_PROJECTDIR)/llvm "-DLLVM_TARGETS_TO_BUILD=X86;ARM;AArch64;RISCV;WebAssembly" "-DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=AVR;Xtensa" -DCMAKE_BUILD_TYPE=Release -DLIBCLANG_BUILD_STATIC=ON -DLLVM_ENABLE_TERMINFO=OFF -DLLVM_ENABLE_ZLIB=OFF -DLLVM_ENABLE_LIBEDIT=OFF -DLLVM_ENABLE_Z3_SOLVER=OFF -DLLVM_ENABLE_OCAMLDOC=OFF -DLLVM_ENABLE_LIBXML2=OFF -DLLVM_ENABLE_PROJECTS="clang;lld" -DLLVM_TOOL_CLANG_TOOLS_EXTRA_BUILD=OFF -DCLANG_ENABLE_STATIC_ANALYZER=OFF -DCLANG_ENABLE_ARCMT=OFF $(LLVM_OPTION)
Makefile: automatically build LLVM when needed
6 years ago
# Build LLVM.
Makefile: using an alternative LLVM build dir now works
6 years ago
$(LLVM_BUILDDIR): $(LLVM_BUILDDIR)/build.ninja
internal/task: use asyncify on webassembly This change implements a new "scheduler" for WebAssembly using binaryen's asyncify transform. This is more reliable than the current "coroutines" transform, and works with non-Go code in the call stack. runtime (js/wasm): handle scheduler nesting If WASM calls into JS which calls back into WASM, it is possible for the scheduler to nest. The event from the callback must be handled immediately, so the task cannot simply be deferred to the outer scheduler. This creates a minimal scheduler loop which is used to handle such nesting.
3 years ago
cd $(LLVM_BUILDDIR) && ninja $(NINJA_BUILD_TARGETS)
Makefile: automatically build LLVM when needed
6 years ago
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
ifneq ($(USE_SYSTEM_BINARYEN),1)
internal/task: use asyncify on webassembly This change implements a new "scheduler" for WebAssembly using binaryen's asyncify transform. This is more reliable than the current "coroutines" transform, and works with non-Go code in the call stack. runtime (js/wasm): handle scheduler nesting If WASM calls into JS which calls back into WASM, it is possible for the scheduler to nest. The event from the callback must be handled immediately, so the task cannot simply be deferred to the outer scheduler. This creates a minimal scheduler loop which is used to handle such nesting.
3 years ago
# Build Binaryen
.PHONY: binaryen
ci: fix Binaryen cache on Windows The wrong path was used to cache binaryen, so it wasn't actually getting cached. Therefore, wasm-opt was rebuilt on every new PR (slowing down the "Build TinyGo release tarball" a lot).
3 years ago
binaryen: build/wasm-opt$(EXE)
build/wasm-opt$(EXE):
housekeeping: wasm optional in smoketest and fix make clean
3 years ago
mkdir -p build
ci: only build wasm-opt, don't build other Binaryen tools
3 years ago
cd lib/binaryen && cmake -G Ninja . -DBUILD_STATIC_LIB=ON $(BINARYEN_OPTION) && ninja bin/wasm-opt$(EXE)
ci: fix Binaryen cache on Windows The wrong path was used to cache binaryen, so it wasn't actually getting cached. Therefore, wasm-opt was rebuilt on every new PR (slowing down the "Build TinyGo release tarball" a lot).
3 years ago
cp lib/binaryen/bin/wasm-opt$(EXE) build/wasm-opt$(EXE)
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
endif
Makefile: automatically build LLVM when needed
6 years ago
wasm: include wasi-libc This allows CGo code to call some libc functions. Additionally, by putting memset/memmove/memcpy in an archive they're not included anymore when not necessary, reducing code size for small programs.
5 years ago
# Build wasi-libc sysroot
.PHONY: wasi-libc
wasi-libc: lib/wasi-libc/sysroot/lib/wasm32-wasi/libc.a
lib/wasi-libc/sysroot/lib/wasm32-wasi/libc.a:
Makefile: check whether submodules have been downloaded in some common cases This should help new people making this very common mistake.
4 years ago
@if [ ! -e lib/wasi-libc/Makefile ]; then echo "Submodules have not been downloaded. Please download them using:\n git submodule update --init"; exit 1; fi
wasm: update wasi-libc dependency The latest version allows overriding the default CFLAGS. By default, they're `-O2 -DNDEBUG`, thus not including DWARF debug information. This commit changes this to include the `-g` flag. Apart from an improved debug experience, this lets -size=full attribute code to wasi-libc. Before: $ tinygo build -o test.wasm -size=full ./testdata/alias.go code rodata data bss | flash ram | package ------------------------------- | --------------- | ------- 1780 0 188 130733 | 1968 130921 | (unknown) 84 0 0 0 | 84 0 | internal/task 281 0 0 0 | 281 0 | main 2374 0 4 147 | 2378 151 | runtime ------------------------------- | --------------- | ------- 4519 0 192 130880 | 4711 131072 | total After: $ tinygo build -o test.wasm -size=full ./testdata/alias.go code rodata data bss | flash ram | package ------------------------------- | --------------- | ------- 40 0 188 130733 | 228 130921 | (unknown) 1740 0 0 0 | 1740 0 | C wasi-libc 84 0 0 0 | 84 0 | internal/task 281 0 0 0 | 281 0 | main 2374 0 4 147 | 2378 151 | runtime ------------------------------- | --------------- | ------- 4519 0 192 130880 | 4711 131072 | total The main difference here is the `(unknown)` code, which turns out to be mostly wasi-libc in this trivial example.
3 years ago
cd lib/wasi-libc && make -j4 WASM_CFLAGS="-O2 -g -DNDEBUG" WASM_CC=$(CLANG) WASM_AR=$(LLVM_AR) WASM_NM=$(LLVM_NM)
wasm: include wasi-libc This allows CGo code to call some libc functions. Additionally, by putting memset/memmove/memcpy in an archive they're not included anymore when not necessary, reducing code size for small programs.
5 years ago
Be able to actually run the blinky example on an nRF runtime.Sleep() doesn't work yet so it prints a lot of data. Also, this depends on a small patch to nrfx.
7 years ago
# Build the Go compiler.
all: add support for Windows
6 years ago
tinygo:
Makefile: use the LLVM monorepo The -DLLVM_TOOL_CLANG_TOOLS_EXTRA_BUILD=OFF option turning off the building of the extra clang tools is required, otherwise linking the tinygo binary fails.
5 years ago
@if [ ! -f "$(LLVM_BUILDDIR)/bin/llvm-config" ]; then echo "Fetch and build LLVM first by running:"; echo " make llvm-source"; echo " make $(LLVM_BUILDDIR)"; exit 1; fi
main: embed git-hash in tinygo-dev executable
4 years ago
CGO_CPPFLAGS="$(CGO_CPPFLAGS)" CGO_CXXFLAGS="$(CGO_CXXFLAGS)" CGO_LDFLAGS="$(CGO_LDFLAGS)" $(GO) build -buildmode exe -o build/tinygo$(EXE) -tags byollvm -ldflags="-X main.gitSha1=`git rev-parse --short HEAD`" .
all: add static and release Makefile targets
6 years ago
wasm: include wasi-libc This allows CGo code to call some libc functions. Additionally, by putting memset/memmove/memcpy in an archive they're not included anymore when not necessary, reducing code size for small programs.
5 years ago
test: wasi-libc
ci: move all cross compilation tests to Linux The idea here is as follows: - Run all Linux and cross compilation tests in the asser-test-linux job. - Only run native tests on MacOS and Windows. This reduces testing time on MacOS and Windows, which are generally more expensive in CI. Also, by not duplicating tests in Windows and MacOS we can reduce overall CI usage a bit. I've also changed the assert-test-linux job a bit to so that the tests that are more likely to break and the tests that are only run in assert-test-linux are run first.
3 years ago
CGO_CPPFLAGS="$(CGO_CPPFLAGS)" CGO_CXXFLAGS="$(CGO_CXXFLAGS)" CGO_LDFLAGS="$(CGO_LDFLAGS)" $(GO) test $(GOTESTFLAGS) -timeout=20m -buildmode exe -tags byollvm ./builder ./cgo ./compileopts ./compiler ./interp ./transform .
Makefile: automatically build LLVM when needed
6 years ago
Makefile: tinygo-test: move slow tests to end, add -fast target to skip them
3 years ago
# Tests that take over a minute in wasi
TEST_PACKAGES_SLOW = \
Makefile: add more TEST_PACKAGES that currently pass
3 years ago
compress/bzip2 \
Makefile: add compress/flate and compress/zlib to wasi test packages
3 years ago
compress/flate \
Makefile: tinygo-test: move slow tests to end, add -fast target to skip them
3 years ago
crypto/dsa \
index/suffixarray \
TEST_PACKAGES_BASE = \
Makefile: add compress/flate and compress/zlib to wasi test packages
3 years ago
compress/zlib \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
container/heap \
container/list \
container/ring \
crypto/des \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
crypto/elliptic/internal/fiat \
crypto/internal/subtle \
compiler: add aliases for many hashing packages This commit adds support for the following packages: - crypto/md5 - crypto/sha1 - crypto/sha256 - crypto/sha512 They would normally need assembly implementations, but with these aliases they already work everywhere.
3 years ago
crypto/md5 \
Makefile: add more TEST_PACKAGES that currently pass
3 years ago
crypto/rc4 \
compiler: add aliases for many hashing packages This commit adds support for the following packages: - crypto/md5 - crypto/sha1 - crypto/sha256 - crypto/sha512 They would normally need assembly implementations, but with these aliases they already work everywhere.
3 years ago
crypto/sha1 \
crypto/sha256 \
crypto/sha512 \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
debug/macho \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
encoding \
encoding/ascii85 \
encoding/base32 \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
encoding/csv \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
encoding/hex \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
go/scanner \
Makefile: add more TEST_PACKAGES that currently pass
3 years ago
hash \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
hash/adler32 \
hash/crc64 \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
hash/fnv \
Makefile: add more TEST_PACKAGES that currently pass
3 years ago
html \
net/ip, syscall/errno: Reduce code duplication by switching to internal/itoa. internal/itoa wasn't around back in go 1.12 days when tinygo's syscall/errno.go was written. It was only added as of go 1.17 ( https://github.com/golang/go/commit/061a6903a232cb868780b ) so we have to have an internal copy for now. The internal copy should be deleted when tinygo drops support for go 1.16. FWIW, the new version seems nicer. It uses no allocations when converting 0, and although the optimizer might make this moot, uses a multiplication x 10 instead of a mod operation.
3 years ago
internal/itoa \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
internal/profile \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
math \
math/cmplx \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
net/http/internal/ascii \
reflect: add support for DeepEqual The implementation has been mostly copied from the Go reference implementation with some small changes to fit TinyGo. Source: https://github.com/golang/go/blob/77a11c05d6a6f766c75f804ea9b8796f9a9f85a3/src/reflect/deepequal.go In addition, this commit also contains the following: - A set of tests copied from the Go reflect package. - An increased stack size for the riscv-qemu and hifive1-qemu targets (because they otherwise fail to run the tests). Because these targets are only used for testing, this seems fine to me.
4 years ago
net/mail \
When running tests under wasmtime, provide a fresh TMPDIR. Also fix a couple os tests that wrote to current directory to write to os.TempDir() instead. After this, os tests pass in wasi, so add them to the list run by "make tinygo-test-wasi".
3 years ago
os \
os: stub out support for some more features This is necessary for the following: - to make sure os/exec can be imported - to make sure internal/testenv can be imported The internal/testenv package (which imports os/exec) is used by a lot of tests. By adding support for it, more tests can be run. This commit adds a bunch of new packages that now pass all tests.
4 years ago
path \
reflect: add support for DeepEqual The implementation has been mostly copied from the Go reference implementation with some small changes to fit TinyGo. Source: https://github.com/golang/go/blob/77a11c05d6a6f766c75f804ea9b8796f9a9f85a3/src/reflect/deepequal.go In addition, this commit also contains the following: - A set of tests copied from the Go reflect package. - An increased stack size for the riscv-qemu and hifive1-qemu targets (because they otherwise fail to run the tests). Because these targets are only used for testing, this seems fine to me.
4 years ago
reflect \
sync: add tests
3 years ago
sync \
testing: test testing package using `tinygo test`
3 years ago
testing \
Makefile: add more TEST_PACKAGES that currently pass
3 years ago
testing/iotest \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
text/scanner \
Makefile: add more TEST_PACKAGES that currently pass
3 years ago
unicode \
reflect: add support for DeepEqual The implementation has been mostly copied from the Go reference implementation with some small changes to fit TinyGo. Source: https://github.com/golang/go/blob/77a11c05d6a6f766c75f804ea9b8796f9a9f85a3/src/reflect/deepequal.go In addition, this commit also contains the following: - A set of tests copied from the Go reflect package. - An increased stack size for the riscv-qemu and hifive1-qemu targets (because they otherwise fail to run the tests). Because these targets are only used for testing, this seems fine to me.
4 years ago
unicode/utf16 \
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
unicode/utf8 \
Makefile: add tinygo-test-wasi; like tinygo-test but with -target wasi
3 years ago
# Standard library packages that pass tests natively
Makefile: exclude archive/zip from TEST_PACKAGES on windows until ReadAt supported
3 years ago
TEST_PACKAGES := \
Makefile: add compress/flate and compress/zlib to wasi test packages
3 years ago
$(TEST_PACKAGES_BASE)
Makefile: add tinygo-test-wasi; like tinygo-test but with -target wasi
3 years ago
Makefile: exclude archive/zip from TEST_PACKAGES on windows until ReadAt supported
3 years ago
# archive/zip requires ReadAt, which is not yet supported on windows
ifneq ($(OS),Windows_NT)
TEST_PACKAGES := \
$(TEST_PACKAGES) \
archive/zip
endif
Makefile: add tinygo-test-wasi; like tinygo-test but with -target wasi
3 years ago
# Standard library packages that pass tests on wasi
TEST_PACKAGES_WASI = \
$(TEST_PACKAGES_BASE)
ci: run `tinygo test` for known-working packages These packages are known to pass tests with `tinygo test`. It's still a very short list, but hopefully this list can be expanded to eventually cover most or all of the standard library.
4 years ago
# Test known-working standard library packages.
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
# TODO: parallelize, and only show failing tests (no implied -v flag).
ci: run `tinygo test` for known-working packages These packages are known to pass tests with `tinygo test`. It's still a very short list, but hopefully this list can be expanded to eventually cover most or all of the standard library.
4 years ago
.PHONY: tinygo-test
Add test command to tinygo (#243) * Add test command to tinygo
5 years ago
tinygo-test:
Makefile: tinygo-test: move slow tests to end, add -fast target to skip them
3 years ago
$(TINYGO) test $(TEST_PACKAGES) $(TEST_PACKAGES_SLOW)
tinygo-test-fast:
main: match `go test` output This commit makes the output of `tinygo test` similar to that of `go test`. It changes the following things in the process: * Running multiple tests in a single command is now possible. They aren't paralellized yet. * Packages with no test files won't crash TinyGo, instead it logs it in the same way the Go toolchain does.
4 years ago
$(TINYGO) test $(TEST_PACKAGES)
testing: support b.SetBytes(); implement sub-benchmarks.
3 years ago
tinygo-bench:
Makefile: tinygo-test: move slow tests to end, add -fast target to skip them
3 years ago
$(TINYGO) test -bench . $(TEST_PACKAGES) $(TEST_PACKAGES_SLOW)
tinygo-bench-fast:
testing: support b.SetBytes(); implement sub-benchmarks.
3 years ago
$(TINYGO) test -bench . $(TEST_PACKAGES)
Makefile: add tinygo-test-wasi; like tinygo-test but with -target wasi
3 years ago
tinygo-test-wasi:
Makefile: tinygo-test: move slow tests to end, add -fast target to skip them
3 years ago
$(TINYGO) test -target wasi $(TEST_PACKAGES_WASI) $(TEST_PACKAGES_SLOW)
tinygo-test-wasi-fast:
Makefile: add tinygo-test-wasi; like tinygo-test but with -target wasi
3 years ago
$(TINYGO) test -target wasi $(TEST_PACKAGES_WASI)
testing: support b.SetBytes(); implement sub-benchmarks.
3 years ago
tinygo-bench-wasi:
Makefile: tinygo-test: move slow tests to end, add -fast target to skip them
3 years ago
$(TINYGO) test -target wasi -bench . $(TEST_PACKAGES_WASI) $(TEST_PACKAGES_SLOW)
tinygo-bench-wasi-fast:
testing: support b.SetBytes(); implement sub-benchmarks.
3 years ago
$(TINYGO) test -target wasi -bench . $(TEST_PACKAGES_WASI)
Add test command to tinygo (#243) * Add test command to tinygo
5 years ago
main (test): integrate test corpus runner This allows us to test a large corpus of external packages against the compiler.
3 years ago
# Test external packages in a large corpus.
test-corpus:
CGO_CPPFLAGS="$(CGO_CPPFLAGS)" CGO_CXXFLAGS="$(CGO_CXXFLAGS)" CGO_LDFLAGS="$(CGO_LDFLAGS)" $(GO) test $(GOTESTFLAGS) -timeout=1h -buildmode exe -tags byollvm -run TestCorpus . -corpus=testdata/corpus.yaml
test-corpus-fast:
CGO_CPPFLAGS="$(CGO_CPPFLAGS)" CGO_CXXFLAGS="$(CGO_CXXFLAGS)" CGO_LDFLAGS="$(CGO_LDFLAGS)" $(GO) test $(GOTESTFLAGS) -timeout=1h -buildmode exe -tags byollvm -run TestCorpus -short . -corpus=testdata/corpus.yaml
test-corpus-wasi: wasi-libc
CGO_CPPFLAGS="$(CGO_CPPFLAGS)" CGO_CXXFLAGS="$(CGO_CXXFLAGS)" CGO_LDFLAGS="$(CGO_LDFLAGS)" $(GO) test $(GOTESTFLAGS) -timeout=1h -buildmode exe -tags byollvm -run TestCorpus . -corpus=testdata/corpus.yaml -target=wasi
ci: make smoketests more flexible
5 years ago
.PHONY: smoketest
smoketest:
ci: build with Go 1.13 on Windows The default Go version is 1.12. Because Go 1.13 introduced language changes (improved numeric constants), TinyGo compiled with Go 1.12 cannot handle Go 1.13 code such as the Go 1.13 standard library. Use Go 1.13 to build TinyGo on Azure Pipelines to fix this.
5 years ago
$(TINYGO) version
os: add stubs for Readlink and File.Seek for baremetal targets, with smoke test. Test currently enabled on pybadge (chosen at random) TODO: - enable test on arduino; currently fails with "interp: ptrtoint integer size..." (#2389) - enable test on nintendoswitch; currently fails with many missing definitions (#2530)
3 years ago
# regression test for #2563
cd tests/os/smoke && $(TINYGO) test -c -target=pybadge && rm smoke.test
avr: use standard pin numbering This commit changes pin numbering for atmega328 based boards (Uno, Nano) to use the standard format, where pin number is determined by the pin/port. Previously, pin numbers were based on what the Uno uses, which does not seem to have a clear pattern. One difference is that counting starts at port B, as there is no port A. So PB0 is 0, PB1 is 1… PC0 is 8. This commit also moves PWM code to the atmega328 file, as it may not be generic to all ATmega chips.
5 years ago
# test all examples (except pwm)
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/adc
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/blinkm
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/blinky2
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/button
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/button2
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/echo
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=circuitplay-express examples/i2s
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/mcp3008
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
runtime: expose memory stats
3 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/memstats
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=microbit examples/microbit-blink
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
nrf: add support for pin change interrupts
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/pininterrupt
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/serial
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
Makefile: add systick example to smoke tests This makes sure future changes will at least keep the example code compiling.
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/systick
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 examples/test
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
# test simulated boards on play.tinygo.org
housekeeping: wasm optional in smoketest and fix make clean
3 years ago
ifneq ($(WASM), 0)
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o test.wasm -tags=arduino examples/blinky1
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
@$(MD5SUM) test.wasm
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o test.wasm -tags=hifive1b examples/blinky1
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
@$(MD5SUM) test.wasm
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o test.wasm -tags=reelboard examples/blinky1
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
@$(MD5SUM) test.wasm
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o test.wasm -tags=pca10040 examples/blinky2
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
@$(MD5SUM) test.wasm
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o test.wasm -tags=pca10056 examples/blinky2
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
@$(MD5SUM) test.wasm
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o test.wasm -tags=circuitplay_express examples/blinky1
targets: simulate Circuit Playground Express in play.tinygo.org This requires a number of changes to atsamd21 code. It's not a very clean separation, but I couldn't come up with a better one.
5 years ago
@$(MD5SUM) test.wasm
housekeeping: wasm optional in smoketest and fix make clean
3 years ago
endif
Makefile: add simulated boards to smoke tests One board (pca10040) was already tested. To make sure stuff doesn't break in the future, test all the other boards too.
5 years ago
# test all targets/boards
nrf: add support for SoftDevices to PCA10040 board
6 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040-s132v6 examples/blinky1
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=microbit examples/echo
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
nrf: add microbit-s110v8 target This makes it possible to use Bluetooth on the BBC micro:bit. Note that you need to use -programmer=cmsis-dap otherwise the SoftDevice will be erased while flashing something that uses Bluetooth.
5 years ago
$(TINYGO) build -size short -o test.hex -target=microbit-s110v8 examples/echo
@$(MD5SUM) test.hex
microbit-v2: add support for S113 SoftDevice This currently doesn't work with `tinygo flash` yet (even with `-programmer=openocd`), you can use pyocd instead. For example, from the Bluetooth package: tinygo build -o test.hex -target=microbit-v2-s113v7 ./examples/advertisement/ pyocd flash --target=nrf52 test.hex I intend to add support for pyocd to work around this issue, so that a simple `tinygo flash` suffices.
4 years ago
$(TINYGO) build -size short -o test.hex -target=microbit-v2 examples/microbit-blink
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=microbit-v2-s113v7 examples/microbit-blink
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=nrf52840-mdk examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10031 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=reelboard examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=reelboard examples/blinky2
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10056 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10056 examples/blinky2
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
initial support for pca10059 Using the official USB Vendor name even for other boards.
4 years ago
$(TINYGO) build -size short -o test.hex -target=pca10059 examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=pca10059 examples/blinky2
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=itsybitsy-m0 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=feather-m0 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=trinket-m0 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=circuitplay-express examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
targets: add target circuitplay-bluefruit Add a target for the Adafruit Circuit Playground Bluefruit, which is based on the nRF52840. Adds the necessary code for the machine package and the json and linker script files in the targets directory. The machine package code is based on board_circuitplay_express.go, with modifications made by consulting the wiring diagram on the adafruit website here: https://learn.adafruit.com/adafruit-circuit-playground-bluefruit/downloads Also adds support to the uf2 conversion packacge to set the familyID field. The Circuit Playground Bluefruit firmware rejects uf2 files without the family id set to 0xADA52840 (and without the flag specifying that the family id is present).
5 years ago
$(TINYGO) build -size short -o test.hex -target=circuitplay-bluefruit examples/blinky1
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=circuitplay-express examples/i2s
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
all: replace underscores with dashes in target names This is the convention, so use it everywhere.
4 years ago
$(TINYGO) build -size short -o test.hex -target=clue-alpha examples/blinky1
machine: add Adafruit CLUE Alpha
5 years ago
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.gba -target=gameboy-advance examples/gba-display
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.gba
atsamd51: fix PWM support in atsamd51p20 This change is related to the following commit 72acda22b0a8d137405e41e9ed54cbfbcce7b26f
4 years ago
$(TINYGO) build -size short -o test.hex -target=grandcentral-m4 examples/blinky1
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=itsybitsy-m4 examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
Adding Board: Feather M4 Express (#688) * machine/feather-m4: Adding Feather M4
5 years ago
$(TINYGO) build -size short -o test.hex -target=feather-m4 examples/blinky1
@$(MD5SUM) test.hex
Added Adafruit's pybadge target (#795) * machine/pybadge: add support for Adafruit PyBadge board
5 years ago
$(TINYGO) build -size short -o test.hex -target=pybadge examples/blinky1
@$(MD5SUM) test.hex
Adding Support for Adafruit Metro M4 Express Airlift (#694) * machine/metro-m4: add support for Adafruit Metro M4 Express Airlift board
5 years ago
$(TINYGO) build -size short -o test.hex -target=metro-m4-airlift examples/blinky1
@$(MD5SUM) test.hex
Adafruit PyPortal Support (#800) * machine/PyPortal: implementation, also includes refinements for other members of samd51x familty.
5 years ago
$(TINYGO) build -size short -o test.hex -target=pyportal examples/blinky1
@$(MD5SUM) test.hex
Add smoke tests
5 years ago
$(TINYGO) build -size short -o test.hex -target=particle-argon examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=particle-boron examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=particle-xenon examples/blinky1
@$(MD5SUM) test.hex
nrf: add support for the PineTime64 devkit This smartwatch doesn't have an on-board debugger, so I picked the one I was using while getting this smartwatch to run Go programs (the J-Link EDU Mini).
5 years ago
$(TINYGO) build -size short -o test.hex -target=pinetime-devkit0 examples/blinky1
@$(MD5SUM) test.hex
machine: add support for the X9 Pro smartwatch This is a Chinese smart watch sold on AliExpress etc. It is based on a nrf52832. More information: https://github.com/curtpw/nRF5x-device-reverse-engineering/tree/master/X9-nrf52832-activity-tracker
5 years ago
$(TINYGO) build -size short -o test.hex -target=x9pro examples/blinky1
@$(MD5SUM) test.hex
nrf: support for SoftDevice s140 PCA10056 board
5 years ago
$(TINYGO) build -size short -o test.hex -target=pca10056-s140v7 examples/blinky1
@$(MD5SUM) test.hex
reelboard: add SoftDevice target reelboard-s140v7 Unfortunately, `tinygo flash` doesn't work here. You have to merge the SoftDevice and the application hex with a mergehex tool and flash that to the board.
5 years ago
$(TINYGO) build -size short -o test.hex -target=reelboard-s140v7 examples/blinky1
@$(MD5SUM) test.hex
Seeed WioTerminal support (#1124) * machine/wioterminal: add support for wioterminal board
4 years ago
$(TINYGO) build -size short -o test.hex -target=wioterminal examples/blinky1
@$(MD5SUM) test.hex
Added Adafruit PyGamer Target (#1173) * machine/PyGamer: add board support
4 years ago
$(TINYGO) build -size short -o test.hex -target=pygamer examples/blinky1
machine/samd21: basic implementation for DAC (#1183) * machine/samd21: basic DAC implementation Signed-off-by: Ron Evans <ron@hybridgroup.com>
4 years ago
@$(MD5SUM) test.hex
Seeed XIAO support (#1170) * machine/xiao: add support for Seeedstudio XIAO board
4 years ago
$(TINYGO) build -size short -o test.hex -target=xiao examples/blinky1
Added Adafruit PyGamer Target (#1173) * machine/PyGamer: add board support
4 years ago
@$(MD5SUM) test.hex
machine/samd21: basic implementation for DAC (#1183) * machine/samd21: basic DAC implementation Signed-off-by: Ron Evans <ron@hybridgroup.com>
4 years ago
$(TINYGO) build -size short -o test.hex -target=circuitplay-express examples/dac
@$(MD5SUM) test.hex
machine/samd51: add DAC support (#1198) * machine/samd51: add DAC support
4 years ago
$(TINYGO) build -size short -o test.hex -target=pyportal examples/dac
@$(MD5SUM) test.hex
machine/feather-nrf52840: add smoketest for Adafruit Feather nrf52840 board Signed-off-by: deadprogram <ron@hybridgroup.com>
4 years ago
$(TINYGO) build -size short -o test.hex -target=feather-nrf52840 examples/blinky1
@$(MD5SUM) test.hex
machine/feather-nrf52840-sense: add board definition for Adafruit Feather nRF52840 Sense
3 years ago
$(TINYGO) build -size short -o test.hex -target=feather-nrf52840-sense examples/blinky1
@$(MD5SUM) test.hex
machine/itsybitsy-nrf52840: add support for Adafruit Itsybitsy nrf52840 (#1243) * machine/itsybitsy-nrf52840: add support for Adafruit Itsybitsy nrf52840 Express board
4 years ago
$(TINYGO) build -size short -o test.hex -target=itsybitsy-nrf52840 examples/blinky1
@$(MD5SUM) test.hex
qtpy: add pin for neopixels
3 years ago
$(TINYGO) build -size short -o test.hex -target=qtpy examples/serial
machine/qtpy: add board definition for Adafruit QTPy Signed-off-by: deadprogram <ron@hybridgroup.com>
4 years ago
@$(MD5SUM) test.hex
teensy40: initial implementation
4 years ago
$(TINYGO) build -size short -o test.hex -target=teensy40 examples/blinky1
@$(MD5SUM) test.hex
teensy36: add to smoketest This required some changes to the UART code to get it to compile on Go 1.11.
4 years ago
$(TINYGO) build -size short -o test.hex -target=teensy36 examples/blinky1
@$(MD5SUM) test.hex
machine/p1am-100: rename MISO/MOSI This makes p1am-100 work again after commit d1c4ed6.
4 years ago
$(TINYGO) build -size short -o test.hex -target=p1am-100 examples/blinky1
@$(MD5SUM) test.hex
atsame54: add initial support for atsame54-xpro
4 years ago
$(TINYGO) build -size short -o test.hex -target=atsame54-xpro examples/blinky1
@$(MD5SUM) test.hex
atsame5x: add support for CAN
4 years ago
$(TINYGO) build -size short -o test.hex -target=atsame54-xpro examples/can
@$(MD5SUM) test.hex
atsame51: add initial support for feather-m4-can
4 years ago
$(TINYGO) build -size short -o test.hex -target=feather-m4-can examples/blinky1
@$(MD5SUM) test.hex
atsame5x: add support for CAN
4 years ago
$(TINYGO) build -size short -o test.hex -target=feather-m4-can examples/caninterrupt
@$(MD5SUM) test.hex
machine: define Serial as the default output Previously, the machine.UART0 object had two meanings: - it was the first UART on the chip - it was the default output for println These two meanings conflict, and resulted in workarounds like: - Defining UART0 to refer to the USB-CDC interface (atsamd21, atsamd51, nrf52840), even though that clearly isn't an UART. - Defining NRF_UART0 to avoid a conflict with UART0 (which was redefined as a USB-CDC interface). - Defining aliases like UART0 = UART1, which refer to the same hardware peripheral (stm32). This commit changes this to use a new machine.Serial object for the default serial port. It might refer to the first or second UART depending on the board, or even to the USB-CDC interface. Also, UART0 now really refers to the first UART on the chip, no longer to a USB-CDC interface. The changes in the runtime package are all just search+replace. The changes in the machine package are a mixture of search+replace and manual modifications. This commit does not affect binary size, in fact it doesn't affect the resulting binary at all.
4 years ago
$(TINYGO) build -size short -o test.hex -target=arduino-nano33 examples/blinky1
@$(MD5SUM) test.hex
machine/arduino_mkrwifi1010: add board definition for Arduino MKR WiFi 1010
3 years ago
$(TINYGO) build -size short -o test.hex -target=arduino-mkrwifi1010 examples/blinky1
@$(MD5SUM) test.hex
smoke&readme: add missing boards
3 years ago
$(TINYGO) build -size short -o test.hex -target=pico examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=nano-33-ble examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=nano-rp2040 examples/blinky1
add rp2040, pico adds preliminary support (just enough to run blinky1) for the Raspberry Pi Pico board along with the rp2040 mcu.
4 years ago
@$(MD5SUM) test.hex
rp2040: support Adafruit Feather RP2040
3 years ago
$(TINYGO) build -size short -o test.hex -target=feather-rp2040 examples/blinky1
@$(MD5SUM) test.hex
machine/atsamd51x,runtime/atsamd51x: fixes needed for full support for all PWM pins. Also adds some useful constants to clarify peripheral clock usage Signed-off-by: deadprogram <ron@hybridgroup.com>
4 years ago
# test pwm
$(TINYGO) build -size short -o test.hex -target=itsybitsy-m0 examples/pwm
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=itsybitsy-m4 examples/pwm
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=feather-m4 examples/pwm
@$(MD5SUM) test.hex
Group together STM32 smoke tests. And then allow them to be disabled with one option.
4 years ago
ifneq ($(STM32), 0)
$(TINYGO) build -size short -o test.hex -target=bluepill examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=feather-stm32f405 examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=lgt92 examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=nucleo-f103rb examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=nucleo-f722ze examples/blinky1
@$(MD5SUM) test.hex
stm32: add nucleo-l031k6 support Adds i2c for all L0 series UART, Blinky (LED) and i2c tested
4 years ago
$(TINYGO) build -size short -o test.hex -target=nucleo-l031k6 examples/blinky1
@$(MD5SUM) test.hex
Group together STM32 smoke tests. And then allow them to be disabled with one option.
4 years ago
$(TINYGO) build -size short -o test.hex -target=nucleo-l432kc examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=nucleo-l552ze examples/blinky1
@$(MD5SUM) test.hex
Improvements for stm32wle targets : - board/stm32: Add STM32 Nucleo WL55JC board - stm32/stm32wl: Set 48Mhz HSE32/PLL as default Clock, SPI implementation
3 years ago
$(TINYGO) build -size short -o test.hex -target=nucleo-wl55jc examples/blinky1
@$(MD5SUM) test.hex
Group together STM32 smoke tests. And then allow them to be disabled with one option.
4 years ago
$(TINYGO) build -size short -o test.hex -target=stm32f4disco examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=stm32f4disco examples/blinky2
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=stm32f4disco-1 examples/blinky1
@$(MD5SUM) test.hex
stm32: add pwm for f4 series
4 years ago
$(TINYGO) build -size short -o test.hex -target=stm32f4disco-1 examples/pwm
@$(MD5SUM) test.hex
targets,runtime,machine: add support for the stm32f469-disco board The LEDs and button work; I haven't tested the SPI and I2C configuration.
3 years ago
$(TINYGO) build -size short -o test.hex -target=stm32f469disco examples/blinky1
@$(MD5SUM) test.hex
stm32: add minimal stm32wlex5 / lorae5 target credit to ofauchon
3 years ago
$(TINYGO) build -size short -o test.hex -target=lorae5 examples/blinky1
@$(MD5SUM) test.hex
stm32: add blues wireless swan
3 years ago
$(TINYGO) build -size short -o test.hex -target=swan examples/blinky1
@$(MD5SUM) test.hex
Group together STM32 smoke tests. And then allow them to be disabled with one option.
4 years ago
endif
ci: make smoketests more flexible
5 years ago
ifneq ($(AVR), 0)
avr: add atmega1284 chip support Not tested on actual hardware, only on simavr. The main motivation for adding this chip is to be able to run simulated tests using a much larger memory space (16kB RAM, 128kB flash) without jumping to the XMega devices that may not be as well supported by LLVM.
5 years ago
$(TINYGO) build -size short -o test.hex -target=atmega1284p examples/serial
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=arduino examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
avr: use standard pin numbering This commit changes pin numbering for atmega328 based boards (Uno, Nano) to use the standard format, where pin number is determined by the pin/port. Previously, pin numbers were based on what the Uno uses, which does not seem to have a clear pattern. One difference is that counting starts at port B, as there is no port A. So PB0 is 0, PB1 is 1… PC0 is 8. This commit also moves PWM code to the atmega328 file, as it may not be generic to all ATmega chips.
5 years ago
$(TINYGO) build -size short -o test.hex -target=arduino examples/pwm
@$(MD5SUM) test.hex
avr: add support for tasks scheduler This adds support for the `-scheduler=tasks` flag for AVR. On most AVR chips you wouldn't want to run a real scheduler but it may be useful in some cases, especially on devices with more RAM. It is disabled by default.
5 years ago
$(TINYGO) build -size short -o test.hex -target=arduino -scheduler=tasks examples/blinky1
@$(MD5SUM) test.hex
PWM Support for atmega1280 Add arduino mega 1280 PWM test
4 years ago
$(TINYGO) build -size short -o test.hex -target=arduino-mega1280 examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=arduino-mega1280 examples/pwm
Arduino Mega 1280 support Fix ldflags Update targets/arduino-mega1280.json Co-authored-by: Ayke <aykevanlaethem@gmail.com> Update atmega1280.json Update Makefile
4 years ago
@$(MD5SUM) test.hex
all: add Arduino Nano support
5 years ago
$(TINYGO) build -size short -o test.hex -target=arduino-nano examples/blinky1
@$(MD5SUM) test.hex
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=digispark examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
avr: use a garbage collector This might sound crazy, but I think it's better to enable the GC by default to avoid surprises. It costs 1130 bytes of flash and 16 bytes of RAM (plus heap overhead) so it's not exactly free, but if needed it can easily be disabled with `-gc=leaking`. On the Uno (32kB flash, 2kB RAM) that's not massive, on the DigiSpark (8kB flash, 0.5kB RAM) that may be too much depending on the application.
5 years ago
$(TINYGO) build -size short -o test.hex -target=digispark -gc=leaking examples/blinky1
@$(MD5SUM) test.hex
esp: add support for the Espressif ESP32 chip This is only very minimal support. More support (such as tinygo flash, or peripheral access) should be added in later commits, to keep this one focused. Importantly, this commit changes the LLVM repo from llvm/llvm-project to tinygo-org/llvm-project. This provides a little bit of versioning in case something changes in the Espressif fork. If we want to upgrade to LLVM 11 it's easy to switch back to llvm/llvm-project until Espressif has updated their fork.
4 years ago
endif
ifneq ($(XTENSA), 0)
machine/esp32, targets/esp32: correct board definitions for actual boards not processor variants, also define all labeled pins Signed-off-by: deadprogram <ron@hybridgroup.com>
4 years ago
$(TINYGO) build -size short -o test.bin -target=esp32-mini32 examples/blinky1
esp8266: add support for this chip Many thanks to cnlohr for the nosdk8266 project: https://github.com/cnlohr/nosdk8266
5 years ago
@$(MD5SUM) test.bin
$(TINYGO) build -size short -o test.bin -target=nodemcu examples/blinky1
@$(MD5SUM) test.bin
board: add M5Stack Core2
3 years ago
$(TINYGO) build -size short -o test.bin -target m5stack-core2 examples/serial
@$(MD5SUM) test.bin
board: add M5Stack
3 years ago
$(TINYGO) build -size short -o test.bin -target m5stack examples/serial
@$(MD5SUM) test.bin
all: add HiFive1 rev B board with RISC-V architecture This page has been a big help in adding support for this new chip: https://wiki.osdev.org/HiFive-1_Bare_Bones
6 years ago
endif
esp32c3: add support for this chip This change adds support for the ESP32-C3, a new chip from Espressif. It is a RISC-V core so porting was comparatively easy. Most peripherals are shared with the (original) ESP32 chip, but with subtle differences. Also, the SVD file I've used gives some peripherals/registers a different name which makes sharing code harder. Eventually, when an official SVD file for the ESP32 is released, I expect that a lot of code can be shared between the two chips. More information: https://www.espressif.com/en/products/socs/esp32-c3 TODO: - stack scheduler - interrupts - most peripherals (SPI, I2C, PWM, etc)
3 years ago
$(TINYGO) build -size short -o test.bin -target=esp32c3 examples/serial
@$(MD5SUM) test.bin
board: add M5Stamp C3
3 years ago
$(TINYGO) build -size short -o test.bin -target=m5stamp-c3 examples/serial
@$(MD5SUM) test.bin
try adding assertions to CI
5 years ago
$(TINYGO) build -size short -o test.hex -target=hifive1b examples/blinky1
Makefile: add md5sum to smoketest This makes it much easier to check whether a binary changed at all, to avoid having to test it on real hardware.
5 years ago
@$(MD5SUM) test.hex
all: replace underscores with dashes in target names This is the convention, so use it everywhere.
4 years ago
$(TINYGO) build -size short -o test.hex -target=hifive1-qemu examples/serial
@$(MD5SUM) test.hex
maixbit: add smoke test
4 years ago
$(TINYGO) build -size short -o test.hex -target=maixbit examples/blinky1
@$(MD5SUM) test.hex
housekeeping: wasm optional in smoketest and fix make clean
3 years ago
ifneq ($(WASM), 0)
builder: add support for -size= flag for WebAssembly
3 years ago
$(TINYGO) build -size short -o wasm.wasm -target=wasm examples/wasm/export
$(TINYGO) build -size short -o wasm.wasm -target=wasm examples/wasm/main
housekeeping: wasm optional in smoketest and fix make clean
3 years ago
endif
all: fix -gc=none This option was broken for a long time, in part because we didn't test for it. This commit fixes that and adds a test to make sure it won't break again unnoticed.
4 years ago
# test various compiler flags
$(TINYGO) build -size short -o test.hex -target=pca10040 -gc=none -scheduler=none examples/blinky1
@$(MD5SUM) test.hex
$(TINYGO) build -size short -o test.hex -target=pca10040 -opt=1 examples/blinky1
@$(MD5SUM) test.hex
all: add a flag to the command line to select the serial implementation This can be very useful for some purposes: * It makes it possible to disable the UART in cases where it is not needed or needs to be disabled to conserve power. * It makes it possible to disable the serial output to reduce code size, which may be important for some chips. Sometimes, a few kB can be saved this way. * It makes it possible to override the default, for example you might want to use an actual UART to debug the USB-CDC implementation. It also lowers the dependency on having machine.Serial defined, which is often not defined when targeting a chip. Eventually, we might want to make it possible to write `-target=nrf52` or `-target=atmega328p` for example to target the chip itself with no board specific assumptions. The defaults don't change. I checked this by running `make smoketest` before and after and comparing the results.
3 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 -serial=none examples/echo
@$(MD5SUM) test.hex
nintendoswitch: support outputting .nro files directly By modifying the linker script a bit and adding the NRO0 header directly in the assembly, it's possible to craft an ELF file that can be converted straight to a binary (using objcopy or similar) that is a NRO file. This avoids custom code for NRO files or an extra build step. With another change, .nro files are recognized by TinyGo so that this will create a ready-to-run NRO file: tinygo build -o test.nro -target=nintendoswitch examples/serial
4 years ago
$(TINYGO) build -o test.nro -target=nintendoswitch examples/serial
@$(MD5SUM) test.nro
builder: add support for -opt=0 This optimization level wasn't working before because some passes expect some globals to be cleaned up afterwards. Cleaning these globals is easy, just add the pass necessary for it. This shouldn't reduce the usefulness of the -opt=0 build flag as most optimizations are still skipped.
4 years ago
$(TINYGO) build -size short -o test.hex -target=pca10040 -opt=0 ./testdata/stdlib.go
@$(MD5SUM) test.hex
builder: build static binaries using musl on Linux This commit adds support for musl-libc and uses it by default on Linux. The main benefit of it is that binaries are always statically linked instead of depending on the host libc, even when using CGo. Advantages: - The resulting binaries are always statically linked. - No need for any tools on the host OS, like a compiler, linker, or libc in a release build of TinyGo. - This also simplifies cross compilation as no cross compiler is needed (it's all built into the TinyGo release build). Disadvantages: - Binary size increases by 5-6 kilobytes if -no-debug is used. Binary size increases by a much larger margin when debugging symbols are included (the default behavior) because musl is built with debugging symbols enabled. - Musl does things a bit differently than glibc, and some CGo code might rely on the glibc behavior. - The first build takes a bit longer because musl needs to be built. As an additional bonus, time is now obtained from the system in a way that fixes the Y2038 problem because musl has been a bit more agressive in switching to 64-bit time_t.
5 years ago
GOOS=linux GOARCH=arm $(TINYGO) build -size short -o test.elf ./testdata/cgo
windows: add support for the -size= flag Like WebAssembly, it misses information on strings and other anonymous symbols. However, most code (.text) is covered.
3 years ago
GOOS=windows GOARCH=amd64 $(TINYGO) build -size short -o test.exe ./testdata/cgo
Makefile: add smoke test with gc=leaking to test dead asm code
3 years ago
ifneq ($(OS),Windows_NT)
all: add support for windows/amd64 This uses Mingw-w64, which seems to be the de facto standard for porting Unixy programs to Windows.
3 years ago
# TODO: this does not yet work on Windows. Somehow, unused functions are
# not garbage collected.
Makefile: add smoke test with gc=leaking to test dead asm code
3 years ago
$(TINYGO) build -o test.elf -gc=leaking -scheduler=none examples/serial
endif
ci: move tests from CircleCI config to Makefile This makes it easier to run smoke tests locally.
6 years ago
initial support for pca10059 Using the official USB Vendor name even for other boards.
4 years ago
wasm test suite (#1116) * wasm: add test suite using headlless chrome
5 years ago
wasmtest:
make,builder: incorporate feedback from code review on Go 1.15 update Signed-off-by: deadprogram <ron@hybridgroup.com>
4 years ago
$(GO) test ./tests/wasm
wasm test suite (#1116) * wasm: add test suite using headlless chrome
5 years ago
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
build/release: tinygo gen-device wasi-libc $(if $(filter 1,$(USE_SYSTEM_BINARYEN)),,binaryen)
all: add static and release Makefile targets
6 years ago
@mkdir -p build/release/tinygo/bin
cgo: support builtin #include headers Add support for header files bundled with the compiler by copying them into the release tarball.
6 years ago
@mkdir -p build/release/tinygo/lib/clang/include
all: add static and release Makefile targets
6 years ago
@mkdir -p build/release/tinygo/lib/CMSIS/CMSIS
@mkdir -p build/release/tinygo/lib/compiler-rt/lib
all: add support for windows/amd64 This uses Mingw-w64, which seems to be the de facto standard for porting Unixy programs to Windows.
3 years ago
@mkdir -p build/release/tinygo/lib/mingw-w64/mingw-w64-crt/lib-common
@mkdir -p build/release/tinygo/lib/mingw-w64/mingw-w64-headers/defaults
builder: build static binaries using musl on Linux This commit adds support for musl-libc and uses it by default on Linux. The main benefit of it is that binaries are always statically linked instead of depending on the host libc, even when using CGo. Advantages: - The resulting binaries are always statically linked. - No need for any tools on the host OS, like a compiler, linker, or libc in a release build of TinyGo. - This also simplifies cross compilation as no cross compiler is needed (it's all built into the TinyGo release build). Disadvantages: - Binary size increases by 5-6 kilobytes if -no-debug is used. Binary size increases by a much larger margin when debugging symbols are included (the default behavior) because musl is built with debugging symbols enabled. - Musl does things a bit differently than glibc, and some CGo code might rely on the glibc behavior. - The first build takes a bit longer because musl needs to be built. As an additional bonus, time is now obtained from the system in a way that fixes the Y2038 problem because musl has been a bit more agressive in switching to 64-bit time_t.
5 years ago
@mkdir -p build/release/tinygo/lib/musl/arch
@mkdir -p build/release/tinygo/lib/musl/crt
@mkdir -p build/release/tinygo/lib/musl/src
all: add static and release Makefile targets
6 years ago
@mkdir -p build/release/tinygo/lib/nrfx
all: include picolibc for bare metal targets This is necessary for better CGo support on bare metal. Existing libraries expect to be able to include parts of libc and expect to be able to link to those symbols. Because with this all targets have a working libc, it is now possible to add tests to check that a libc in fact works basically. Not all parts of picolibc are included, such as the math or stdio parts. These should be added later, when needed. This commit also avoids the need for the custom memcpy/memset/memcmp symbols that are sometimes emitted by LLVM. The C library will take care of that.
5 years ago
@mkdir -p build/release/tinygo/lib/picolibc/newlib/libc
cgo: add support for stdio in picolibc and wasi-libc This adds support for stdio in picolibc and fixes wasm_exec.js so that it can also support C puts. With this, C stdout works on all supported platforms.
3 years ago
@mkdir -p build/release/tinygo/lib/picolibc/newlib/libm
wasm: include wasi-libc This allows CGo code to call some libc functions. Additionally, by putting memset/memmove/memcpy in an archive they're not included anymore when not necessary, reducing code size for small programs.
5 years ago
@mkdir -p build/release/tinygo/lib/wasi-libc
build: fix build-library subcommand This subcommand has been broken for a while, since libraries also use the CPU flag. This commit fixes this. Previously, libraries were usable for most Cortex-M cores. But with the addition of the CPU field, I've limited it to three popular cores: the Cortex-M0 (microbit), Cortex-M0+ (atsamd21), and Cortex-M4 (atsamd21, nrf52, and many others). In the future we might consider also building libraries for the current OS/arch so that libraries like musl are already precompiled.
3 years ago
@mkdir -p build/release/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0
@mkdir -p build/release/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0plus
@mkdir -p build/release/tinygo/pkg/thumbv7em-unknown-unknown-eabi-cortex-m4
cgo: support builtin #include headers Add support for header files bundled with the compiler by copying them into the release tarball.
6 years ago
@echo copying source files
Revert "all: use compiler-rt from the llvm-project directory" This reverts commit acdaaa17d8232989d310292a512e70fccdb288a5. See https://github.com/tinygo-org/tinygo/issues/734 for details.
5 years ago
@cp -p build/tinygo$(EXE) build/release/tinygo/bin
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
ifneq ($(USE_SYSTEM_BINARYEN),1)
internal/task: use asyncify on webassembly This change implements a new "scheduler" for WebAssembly using binaryen's asyncify transform. This is more reliable than the current "coroutines" transform, and works with non-Go code in the call stack. runtime (js/wasm): handle scheduler nesting If WASM calls into JS which calls back into WASM, it is possible for the scheduler to nest. The event from the callback must be handled immediately, so the task cannot simply be deferred to the outer scheduler. This creates a minimal scheduler loop which is used to handle such nesting.
3 years ago
@cp -p build/wasm-opt$(EXE) build/release/tinygo/bin
ci (Windows/Mac): use binaryen from scoop/brew The scoop and brew package managers now bundle up-to-date copies of binaryen. As a result, there is no longer a strong need for us to build and package our own copy.
3 years ago
endif
cgo: support builtin #include headers Add support for header files bundled with the compiler by copying them into the release tarball.
6 years ago
@cp -p $(abspath $(CLANG_SRC))/lib/Headers/*.h build/release/tinygo/lib/clang/include
Revert "all: use compiler-rt from the llvm-project directory" This reverts commit acdaaa17d8232989d310292a512e70fccdb288a5. See https://github.com/tinygo-org/tinygo/issues/734 for details.
5 years ago
@cp -rp lib/CMSIS/CMSIS/Include build/release/tinygo/lib/CMSIS/CMSIS
@cp -rp lib/CMSIS/README.md build/release/tinygo/lib/CMSIS
@cp -rp lib/compiler-rt/lib/builtins build/release/tinygo/lib/compiler-rt/lib
@cp -rp lib/compiler-rt/LICENSE.TXT build/release/tinygo/lib/compiler-rt
@cp -rp lib/compiler-rt/README.txt build/release/tinygo/lib/compiler-rt
builder: build static binaries using musl on Linux This commit adds support for musl-libc and uses it by default on Linux. The main benefit of it is that binaries are always statically linked instead of depending on the host libc, even when using CGo. Advantages: - The resulting binaries are always statically linked. - No need for any tools on the host OS, like a compiler, linker, or libc in a release build of TinyGo. - This also simplifies cross compilation as no cross compiler is needed (it's all built into the TinyGo release build). Disadvantages: - Binary size increases by 5-6 kilobytes if -no-debug is used. Binary size increases by a much larger margin when debugging symbols are included (the default behavior) because musl is built with debugging symbols enabled. - Musl does things a bit differently than glibc, and some CGo code might rely on the glibc behavior. - The first build takes a bit longer because musl needs to be built. As an additional bonus, time is now obtained from the system in a way that fixes the Y2038 problem because musl has been a bit more agressive in switching to 64-bit time_t.
5 years ago
@cp -rp lib/musl/arch/aarch64 build/release/tinygo/lib/musl/arch
@cp -rp lib/musl/arch/arm build/release/tinygo/lib/musl/arch
@cp -rp lib/musl/arch/generic build/release/tinygo/lib/musl/arch
@cp -rp lib/musl/arch/i386 build/release/tinygo/lib/musl/arch
@cp -rp lib/musl/arch/x86_64 build/release/tinygo/lib/musl/arch
@cp -rp lib/musl/crt/crt1.c build/release/tinygo/lib/musl/crt
@cp -rp lib/musl/COPYRIGHT build/release/tinygo/lib/musl
@cp -rp lib/musl/include build/release/tinygo/lib/musl
@cp -rp lib/musl/src/env build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/errno build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/exit build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/include build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/internal build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/malloc build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/mman build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/signal build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/stdio build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/string build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/thread build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/time build/release/tinygo/lib/musl/src
@cp -rp lib/musl/src/unistd build/release/tinygo/lib/musl/src
all: add support for windows/amd64 This uses Mingw-w64, which seems to be the de facto standard for porting Unixy programs to Windows.
3 years ago
@cp -rp lib/mingw-w64/mingw-w64-crt/def-include build/release/tinygo/lib/mingw-w64/mingw-w64-crt
@cp -rp lib/mingw-w64/mingw-w64-crt/lib-common/api-ms-win-crt-* build/release/tinygo/lib/mingw-w64/mingw-w64-crt/lib-common
@cp -rp lib/mingw-w64/mingw-w64-crt/lib-common/kernel32.def.in build/release/tinygo/lib/mingw-w64/mingw-w64-crt/lib-common
@cp -rp lib/mingw-w64/mingw-w64-headers/crt/ build/release/tinygo/lib/mingw-w64/mingw-w64-headers
@cp -rp lib/mingw-w64/mingw-w64-headers/defaults/include build/release/tinygo/lib/mingw-w64/mingw-w64-headers/defaults
Revert "all: use compiler-rt from the llvm-project directory" This reverts commit acdaaa17d8232989d310292a512e70fccdb288a5. See https://github.com/tinygo-org/tinygo/issues/734 for details.
5 years ago
@cp -rp lib/nrfx/* build/release/tinygo/lib/nrfx
all: include picolibc for bare metal targets This is necessary for better CGo support on bare metal. Existing libraries expect to be able to include parts of libc and expect to be able to link to those symbols. Because with this all targets have a working libc, it is now possible to add tests to check that a libc in fact works basically. Not all parts of picolibc are included, such as the math or stdio parts. These should be added later, when needed. This commit also avoids the need for the custom memcpy/memset/memcmp symbols that are sometimes emitted by LLVM. The C library will take care of that.
5 years ago
@cp -rp lib/picolibc/newlib/libc/ctype build/release/tinygo/lib/picolibc/newlib/libc
@cp -rp lib/picolibc/newlib/libc/include build/release/tinygo/lib/picolibc/newlib/libc
@cp -rp lib/picolibc/newlib/libc/locale build/release/tinygo/lib/picolibc/newlib/libc
@cp -rp lib/picolibc/newlib/libc/string build/release/tinygo/lib/picolibc/newlib/libc
@cp -rp lib/picolibc/newlib/libc/tinystdio build/release/tinygo/lib/picolibc/newlib/libc
cgo: add support for stdio in picolibc and wasi-libc This adds support for stdio in picolibc and fixes wasm_exec.js so that it can also support C puts. With this, C stdout works on all supported platforms.
3 years ago
@cp -rp lib/picolibc/newlib/libm/common build/release/tinygo/lib/picolibc/newlib/libm
@cp -rp lib/picolibc-stdio.c build/release/tinygo/lib
wasm: include wasi-libc This allows CGo code to call some libc functions. Additionally, by putting memset/memmove/memcpy in an archive they're not included anymore when not necessary, reducing code size for small programs.
5 years ago
@cp -rp lib/wasi-libc/sysroot build/release/tinygo/lib/wasi-libc/sysroot
Revert "all: use compiler-rt from the llvm-project directory" This reverts commit acdaaa17d8232989d310292a512e70fccdb288a5. See https://github.com/tinygo-org/tinygo/issues/734 for details.
5 years ago
@cp -rp src build/release/tinygo/src
@cp -rp targets build/release/tinygo/targets
build: fix build-library subcommand This subcommand has been broken for a while, since libraries also use the CPU flag. This commit fixes this. Previously, libraries were usable for most Cortex-M cores. But with the addition of the CPU field, I've limited it to three popular cores: the Cortex-M0 (microbit), Cortex-M0+ (atsamd21), and Cortex-M4 (atsamd21, nrf52, and many others). In the future we might consider also building libraries for the current OS/arch so that libraries like musl are already precompiled.
3 years ago
./build/tinygo build-library -target=cortex-m0 -o build/release/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0/compiler-rt compiler-rt
./build/tinygo build-library -target=cortex-m0plus -o build/release/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0plus/compiler-rt compiler-rt
./build/tinygo build-library -target=cortex-m4 -o build/release/tinygo/pkg/thumbv7em-unknown-unknown-eabi-cortex-m4/compiler-rt compiler-rt
./build/tinygo build-library -target=cortex-m0 -o build/release/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0/picolibc picolibc
./build/tinygo build-library -target=cortex-m0plus -o build/release/tinygo/pkg/thumbv6m-unknown-unknown-eabi-cortex-m0plus/picolibc picolibc
./build/tinygo build-library -target=cortex-m4 -o build/release/tinygo/pkg/thumbv7em-unknown-unknown-eabi-cortex-m4/picolibc picolibc
ci: build .deb files along with .tar.gz files for Debian
5 years ago
release: build/release
all: add static and release Makefile targets
6 years ago
tar -czf build/release.tar.gz -C build/release tinygo
ci: build .deb files along with .tar.gz files for Debian
5 years ago
deb: build/release
@mkdir -p build/release-deb/usr/local/bin
@mkdir -p build/release-deb/usr/local/lib
cp -ar build/release/tinygo build/release-deb/usr/local/lib/tinygo
ln -sf ../lib/tinygo/bin/tinygo build/release-deb/usr/local/bin/tinygo
main: move TinyGo version to goenv This is needed to make it available to more packages, for caching purposes. For caching, the version itself may not be enough during development. But for regular releases, the version provides some protection against accidentally using a cache entry that is invalid in a newer version.
5 years ago
fpm -f -s dir -t deb -n tinygo -v $(shell grep "const Version = " goenv/version.go | awk '{print $$NF}') -m '@tinygo-org' --description='TinyGo is a Go compiler for small places.' --license='BSD 3-Clause' --url=https://tinygo.org/ --deb-changelog CHANGELOG.md -p build/release.deb -C ./build/release-deb