From: Ian Lance Taylor <iant@golang.org>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: libgo patch committed: Export getm for test
Date: Thu, 22 Jun 2017 22:09:00 -0000 [thread overview]
Message-ID: <CAOyqgcXB2cCV3D=Tji3kiLkeAQy7uFxhqbPJNyArQSZDG93_Ag@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
This patch to libgo exports the getm function so that it can be
referenced by a test (from
runtime/testdata/testprogcgo/dropm_stub.go). The test is not
currently run, but it will be soon. Bootstrapped and ran Go testsuite
on x86_64-pc-linux-gnu. Committed to mainline.
Ian
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 913 bytes --]
Index: gcc/go/gofrontend/MERGE
===================================================================
--- gcc/go/gofrontend/MERGE (revision 249575)
+++ gcc/go/gofrontend/MERGE (working copy)
@@ -1,4 +1,4 @@
-27204e41643f4549c5ed97d48e17912f64c0aa71
+55b2b2dee55bd495a770347daaf858634057ecb0
The first line of this file holds the git revision number of the last
merge done from the gofrontend repository.
Index: libgo/go/runtime/proc.go
===================================================================
--- libgo/go/runtime/proc.go (revision 249565)
+++ libgo/go/runtime/proc.go (working copy)
@@ -37,6 +37,9 @@ import (
//go:linkname globrunqput runtime.globrunqput
//go:linkname pidleget runtime.pidleget
+// Exported for test (see runtime/testdata/testprogcgo/dropm_stub.go).
+//go:linkname getm runtime.getm
+
// Function called by misc/cgo/test.
//go:linkname lockedOSThread runtime.lockedOSThread
reply other threads:[~2017-06-22 22:09 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='CAOyqgcXB2cCV3D=Tji3kiLkeAQy7uFxhqbPJNyArQSZDG93_Ag@mail.gmail.com' \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
/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).