doc/faq: update out-of-date mention of gollvm
gollvm is mentioned elsewhere in the FAQ too, but this specific mention
seems out-of-date now given the state of the project.
Change-Id: I5be12faeaf9ea445fc4c28eecb7583fda0adb457
Reviewed-on: https://go-review.googlesource.com/c/website/+/507959
Reviewed-by: Than McIntosh <thanm@google.com>
Auto-Submit: Eli Bendersky <eliben@google.com>
Run-TryBot: Eli Bendersky <eliben@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Eli Bendersky <eliben@google.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
diff --git a/_content/doc/faq.html b/_content/doc/faq.html
index f66162d..4d8b07d 100644
--- a/_content/doc/faq.html
+++ b/_content/doc/faq.html
@@ -2303,6 +2303,14 @@
</p>
<p>
+The <code>Gccgo</code> compiler is a front end written in C++
+with a recursive descent parser coupled to the
+standard GCC back end. An experimental
+<a href="https://go.googlesource.com/gollvm/">LLVM back end</a> is
+using the same front end.
+</p>
+
+<p>
At the beginning of the project we considered using LLVM for
<code>gc</code> but decided it was too large and slow to meet
our performance goals.
@@ -2310,14 +2318,6 @@
harder to introduce some of the ABI and related changes, such as
stack management, that Go requires but are not part of the standard
C setup.
-A new <a href="https://go.googlesource.com/gollvm/">LLVM implementation</a>
-is starting to come together now, however.
-</p>
-
-<p>
-The <code>Gccgo</code> compiler is a front end written in C++
-with a recursive descent parser coupled to the
-standard GCC back end.
</p>
<p>
