From: Ian Lance Taylor <iant@golang.org>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Add notes for Go to gcc 12 and 13 changes file
Date: Mon, 20 Mar 2023 12:37:19 -0700 [thread overview]
Message-ID: <CAOyqgcXY24C2b_eOZ0qZ56zWZKM5fTd9Au1cdde-A+z+Fv47Mw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 119 bytes --]
I committed this patch to the gcc-wwwdocs repo to add some notes about
Go to the gcc 12 and 13 changes file.
Ian
pat
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1234 bytes --]
e24f9ef56c11c69fc07bddf9a708ea2fc662f2b3
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index c47d3285..d565c217 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -618,7 +618,14 @@ function Multiply (S1, S2 : Sign) return Sign is
</li>
</ul>
-<!-- <h3 id="go">Go</h3> -->
+<h3 id="go">Go</h3>
+
+<ul>
+ <li>GCC 12 provides a complete implementation of the Go 1.18 user
+ packages.</li>
+ <li>Although Go 1.18 includes support for generic programming, that
+ support is not yet available in GCC.</li>
+</ul>
<!-- .................................................................. -->
<h2 id="jit">libgccjit</h2>
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index a4b71ffa..4fae1f7a 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -380,7 +380,14 @@ a work-in-progress.</p>
</li>
</ul>
-<!-- <h3 id="go">Go</h3> -->
+<h3 id="go">Go</h3>
+
+<ul>
+ <li>GCC 13, like GCC 12, provides a complete implementation of the
+ Go 1.18 user packages.</li>
+ <li>Although Go 1.18 includes support for generic programming, that
+ support is not yet available in GCC.</li>
+</ul>
<h3 id="modula2">Modula-2</h3>
<ul>
reply other threads:[~2023-03-20 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOyqgcXY24C2b_eOZ0qZ56zWZKM5fTd9Au1cdde-A+z+Fv47Mw@mail.gmail.com \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).