|
1 | | -# TinyGo |
| 1 | +# TinyGo GCC (abandoned) |
2 | 2 |
|
3 | | -**This project is suspended**. See [Current status](#current-status) below. |
| 3 | +**This project is abandoned**. See [Current status](#current-status) below. |
4 | 4 |
|
5 | 5 | ## What is this? |
6 | 6 |
|
@@ -88,14 +88,12 @@ There are many. |
88 | 88 | At the moment I'm **no longer working on this project**. The main reason is that |
89 | 89 | it turns out that the code `gccgo` produces is relatively bloated and is written |
90 | 90 | specifically for the regular Go runtime, which is optimized for speed and not |
91 | | -RAM/flash usage. I'm investigating different options, like building a frontend |
92 | | -for LLVM (like [llgo](https://github.com/llvm-mirror/llgo), which sadly appears |
93 | | -to be dead). |
94 | | - |
95 | | -I mainly developed this as a proof of concept so I'm not sure how I'll continue, |
96 | | -but I'm happy that it works (to some degree). I'm interested in microcontrollers |
97 | | -and really like the Go language so may actually use it in the future, in which |
98 | | -case I surely will improve it. |
| 91 | +RAM/flash usage. I'm now working on |
| 92 | +[a new implementation based on LLVM](https://github.com/aykevl/tinygo) just like |
| 93 | +[llgo](https://github.com/llvm-mirror/llgo). |
| 94 | + |
| 95 | +This was mostly a proof of concept and I don't expect to be working on it in the |
| 96 | +future, but I'm happy that it works (to some degree). |
99 | 97 |
|
100 | 98 | Also, it depends on gccgo and gccgo seems to be moving to a runtime written in |
101 | 99 | Go, so I might need to adjust to that in the future. |
|
0 commit comments