Skip to content
This repository was archived by the owner on Mar 11, 2019. It is now read-only.

Commit 25beb0c

Browse files
authored
Update README.markdown
This project is really dead and abandoned, not just suspended.
1 parent f6c845e commit 25beb0c

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

README.markdown

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# TinyGo
1+
# TinyGo GCC (abandoned)
22

3-
**This project is suspended**. See [Current status](#current-status) below.
3+
**This project is abandoned**. See [Current status](#current-status) below.
44

55
## What is this?
66

@@ -88,14 +88,12 @@ There are many.
8888
At the moment I'm **no longer working on this project**. The main reason is that
8989
it turns out that the code `gccgo` produces is relatively bloated and is written
9090
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).
9997

10098
Also, it depends on gccgo and gccgo seems to be moving to a runtime written in
10199
Go, so I might need to adjust to that in the future.

0 commit comments

Comments
 (0)